I did the first
smoketest and it worked for the most part. All I did for the smoketest was just mark the 6th step as fail but I also took a few screenshots and there were a few other problems and I wasn't sure if I should have posted those or not.
- So I think it's worth noting that when I did the 3rd step it failed completely when not connected to wifi which is obviously required but the error message is pretty vague and unhelpful because I was about to mark the test as fail until I realized I had wifi off. I had a few screenshots of it but I couldn't email it due to an error and setting up my gmail account was really annoying because the flame is considered an insecure device so I just used the WebIDE to save screenshots that you can see below.
- The 6th step failed because after clicking the link to verify my account I was taken to a sign in page rather than an account homepage and the email itself was supposed to display a link but it didn't appear on my device.
 |
| Verification email had a link but it wasn't visible |
|
 |
| Sign in page instead of homepage |
|
 |
| Email error so I couldn't get a hold of my other screenshots |
|
I'm glad you mentioned the problem you had getting screenshots. It is really important to not only document the process you use for testing, but also the process you use to document your results, since that is actually an essential part of the testing process.
ReplyDeleteWe can help the community by clearing documenting the challenges we face. We may even be able to find solutions to some of these challenges ourselves (we should run them by Matt Gallagher at our Code for NOVA meet ups, for example).
I'm looking forward to applying what you are learning to the LibriFox app development process!
One helpful site I often use for creating email accounts is http://mailinator.com/. Since I am testing on 6 devices I have created a bunch of emails I use just for buddyup testing, and I often have the email name match the device so I can track of things easier.
ReplyDelete