Test Plan for: Product/Application Component
List the objectives/goals of the usability test; what you want to study or to evaluate. Be specific in what you want achieve, to evaluate with this test (e.g. obtain quality or quantitative regarding certain product/application components, accessibility evaluation, heuristic evaluation, cognitive walk-through etc.).
- Assess the overall effectiveness of the product/application for different types of users performing basic, common tasks;
- Identify obstacles to completing a certain task or using a certain component;
- Evaluate consistency and standards;
- Use the References to guide you in writing your objectives.
Use one scenario for each test. Do not use multiple scenarios for a usability test as it can confuse and frustrate the user. The scenarios used in the usability tests have a direct connection with the scenarios built for the personas document.
Write out the tasks for each persona type. Avoid complex tasks. Make sure the user is able to complete the test in the specified time interval. Assign an estimated completion time for each task.
- Task 1 + estimated time to complete it;
- Task 2 + estimated time to complete it;
- Task 3 + estimated time to complete it;
- As many tasks needed.
A user might complete a task in a shorter or greater time than the estimated time. If the completion time exceeds the estimated time then it there is a problem. Also a user might skip the current task thus the completion time would be 0.
These questions could be presented to the user as a questionnaire or verbally asked.
- Question 1;
- Question 2;
- Question 3;
- As many questions needed.
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?".
Written/video/audio notes done attached to the usability test. These notes reflect the user thoughts and frustrations.