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.
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
Updated simpleTests.R
to use new test variables.
#21
Conversation
Saved results & tested to make sure test hasn't failed in each situation, return error on fail.
if(!result$active){ | ||
stop("Test Failed.") | ||
} | ||
## storing this test result to allow us to use active user's email for testing below. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this first test failed for me yesterday, and if if you only test for email and channel, I suspect it will still fail for me.
Which means that we borked what was working behaviour -- fallback to default device.
Aiee. Looks like I overlooked this at first, and we then did similar changes. But if I now look at the remaining change, it really is just one line and some whitespace. So maybe skip this PR? |
My last commit cleans this up so the only remaining changes are the |
Sorry, missed that -- that would have been cleaner. |
Updated
simpleTests.R
to use new test variables.active
variable should beTRUE
, (except for deleted posts) so this variable tell us that the post was posted successfully.to freeze (pun intended) for some reason. (Had to delete app & re-install to have app working again. - Bug report submitted to the Pushbullet folks.)