Test Plan for: Product/Application Component
Persona Type Tested: Primary
Context: at home, updating playlists
Duration: 1 minutes 50 seconds
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 creating "smart" playlists;
- Identify obstacles to completing the creation of a new radio - "smart" playlist;;
- 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;
- Use the References to guide you in writing your objectives.
Scenario
- The user wants to create a new "smart" playlist.
- 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, including the "Radio" section.
- The user selects all the available default criteria for radio creation.
- He adds "Pink Floyd" as a custom search as well.
- He performs a new custom search for "The Beatles".
- He deletes the "Recent albums" criteria.
- Plays the new generated radio.
- Deletes the first three songs from the global player.
Tasks
- Authentication: 30 s;
- Selects all default criterias: 20 s;
- Performs a custom search for "Pink Floyd": 15 s;
- Performs a custom search for "The Beatles": 15 s;
- Deletes the "Recent albums" criteria: 5 s;
- Plays the "smart" playlist: 5 s;
- Deletes the first three songs from the global player: 20 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 choose the criteria for a new "smart" playlist?
- Question 2: How easy was it for you to generate a new "smart" playlist?
- Question 3: What did you think about the manner of deleting songs from the global player? Anything you would change about that?
- Question 4: Was the terminology understandable for you?
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.