Skip to content

Add Fitbit interface tests #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
bpred754 opened this issue Dec 23, 2016 · 1 comment
Open

Add Fitbit interface tests #47

bpred754 opened this issue Dec 23, 2016 · 1 comment
Labels
Task
Milestone
Backlog

Comments

@bpred754
Copy link
Owner

If Fitbit were to change their API it could potentially break Augeo. These tests should verify that Augeo is receiving the correct data in the right format.
@bpred754 bpred754 added the Task label Dec 23, 2016
@bpred754 bpred754 added this to the Release v1.0.0 milestone Dec 23, 2016
@bpred754 bpred754 assigned bpred754 and unassigned bpred754 Dec 23, 2016
@bpred754
Copy link
Owner Author

Currently the Fitbit API authorization code flow requires a web service. After retrieving the code there is a requirement to maintain the state of access tokens via refresh access token requests.

https://community.fitbit.com/t5/Web-API-Development/Lifetime-Access-Tokens-for-Command-Line-Tools/td-p/1141477

https://dev.fitbit.com/docs

It looks like they want to make it easier for command line tools, however it hasn't been released yet. We need to keep an eye out for these changes. As for now, let's hope they don't make any changes to the endpoints Augeo uses...

@bpred754 bpred754 removed this from the Release v1.0.0 milestone Dec 23, 2016
@bpred754 bpred754 added this to the Backlog milestone Jan 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Task
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@bpred754