Test Plan for: Product/Application Component
Persona Type Tested: Primary
Context: at home, updating playlists
Duration: 5 minutes
Complete the following before starting: Greeting and Consent & User Background Information.
Overall Objectives
- Assess the overall effectiveness of the U play3D application for users who are interested in discovering new bands, organizing their discoveries into new playlists, listening to music and sharing their findings with friends;
- Identify obstacles to completing the creation of a new playlist, the addition of songs to it, playing a playlist and sharing it;
- Have an evidence of the users that used the available Tutorial in order to do this task and ask them if it was helpful;
- Evaluate the time it takes users to perform essential tasks such as playlist creation, songs addition, playlist sharing and listening;
- Test if the terminology and the labels make the application easy and clear to use;
- Test the systems response time
Scenario
- The user wants to search for a band that was recommended to him - "Imagine Dragons".
- To accomplish this, he accesses the application via his Google account. He enters his credentials in the login page.
- After authentication, the main menu of the application is visible.
- The user searches for the "Imagine Dragons" band.
- He looks through the results and selects three songs from each search category which he adds to a new playlist.
- After the playlist was completed, he starts listening to it.
- Realizing he really likes this new band, he decides to share this playlist with his friends on Twitter.
Tasks
- Authentication: 30 s;
- Search for the "Imagine Dragons" band: 30 s;
- Skim through the results: 30s;
- Pick three songs for every search result category and add them to a new playlist entitled "Imagine Dragons-playlist": 1 m;
- Play the newly created playlist: 15 s;
- Listen to a song for a couple of seconds then proceed to the next song: 1m 30s;
- Share the playlist on Twitter: 45 s;
Post-test Questions
These questions could be presented to the user as a questionnaire or verbally asked.
- Question 1: How easy was it for you to search for a band?
- Question 2: What did you think about the manner of presenting the search results? Anything you would change about that?
- Question 3: How easy was it for you to navigate through the search result categories?
- Question 4: How easy was it for you to add songs to a playlist?
- Question 5: Did you find the available tutorial helpful in performing this tasks?
- Question 6: Was the terminology understandable for you?
- Question 7: Was the systems response time satisfactory?
Notes for Test Coordinator
- Remind the user that you would like them to 'think aloud' so that you can understand what they are thinking, about the task or the product/application;
- Read the user the scenario for the test;
- Read the user the tasks he has to complete. If the tasks are complex, you may want to put a sheet of paper in front of the user with each task written out;
- Record the user's actions, comments, questions, and body language (write them in the Test Observations section accompanied by video/audio).
- Don't offer help; let the user attempt to perform the task. If they ask for help reply with: "What do you think you/that would do?" "What do you think that means?".
References
- Fluid User Testing;
- usability.gov Templates;
- Handbook of Usability Testing by Jeffrey Rubin;
- A Practical Guide to Usability Testing by Joseph S. Dumas and Janice C. Redish.