While I was home this weekend I asked my father to test my Quick Mechanic App using the paper prototype I made. After a few technical difficulties-ran out of memory on camera and the camera was not compatible with my Mac, we got it done. The good news about the technical difficulties was that it showed me some things that needed to be changed.
In Order to be sure that I reached my goals I wanted a list of questions to ask myself. I came across Atlassian Blogs, “Usability Testing with Paper Prototypes”. Richard Dunmayer and Gert Jan Bartelds, members of Testnet, the Dutch software tester’s association, wrote a guest blog.
Using the questions they provided in the blog, I did my test and recorded my results.
1. Are the end users doing what I want them to do?
Yes, the user did exactly what I wanted.
2. Are they doing what I expected them to do?
They did not do what I expected at first. I made some changes and improved the flow.
3. Did they become confused while trying to reach their goals?
No, he did not seem confused, and was able to reach his goal.
4. Did I really think through all possible paths through the application?
After one of the run throughs I recognized that some paths needed to be added. Once added, I believe the application has all the possible paths.
5. Did they have a preferred path?
The user did not have a preferred path. The application can be used in several ways and he seemed comfotable with all of them.
6. Are some paths unused?
All the paths were used.
7. Are some paths used in ways that weren’t intended?
After the modifications I believe all the paths were used in the way in which I intended.
I think my test went well. I have posted it to YouTube.
Works Cited
Dunmayer, Richard, and Gert Jan Bartelds. “Usability Testing with Paper Prototypes.” Atlassian Blogs. N.p., 30 Nov. 2011. Web. 27 Apr. 2014. <http://blogs.atlassian.com/2011/11/usability-testing-with-paper-prototyping
No comments:
Post a Comment