Usability Testing Plans
2 likes1,165 views
The document outlines the key components of an effective test plan, including defining goals and objectives, research questions, participant characteristics, test methods, tasks, environments, roles, and reporting. An effective test plan ensures the team understands what needs to be tested, provides guidance on running tests, and establishes a common framework for collecting and reporting results.
Usability Testing Plans
- 1. Testing Plans: Mapping the Work Thursday, February 23, 12
- 2. You got to know where you want to go. Thursday, February 23, 12
- 3. Thursday, February 23, 12
- 4. and you got to know where the pitfalls are. Thursday, February 23, 12
- 5. Thursday, February 23, 12
- 6. You need to know Thursday, February 23, 12
- 7. • How • When • Where • Who • Why • What Thursday, February 23, 12
- 8. Worries: Formal? Casual? Thursday, February 23, 12
- 10. Test plans also: Thursday, February 23, 12
- 11. Serve as main communication vehicle Thursday, February 23, 12
- 12. Defines required resources. Thursday, February 23, 12
- 13. Define Focal points Milestones Thursday, February 23, 12
- 14. Parts of the Test Plan Thursday, February 23, 12
- 15. Purpose, goals, and objectives of the test Thursday, February 23, 12
- 16. Broadly. Major stuff. Thursday, February 23, 12
- 17. Why are you testing? What’s the impetus? Thursday, February 23, 12
- 18. Reasons NOT to test: Thursday, February 23, 12
- 19. Thursday, February 23, 12
- 20. • Improving user experience Thursday, February 23, 12
- 21. • Improving user experience • Everyone else is doing it Thursday, February 23, 12
- 22. • Improving user experience • Everyone else is doing it • Space is available Thursday, February 23, 12
- 23. • Improving user experience • Everyone else is doing it • Space is available • Somebody wants to do something shiny Thursday, February 23, 12
- 24. • Improving user experience • Everyone else is doing it • Space is available • Somebody wants to do something shiny • Market testing Thursday, February 23, 12
- 25. Good reasons to test: Thursday, February 23, 12
- 26. • Understanding which users can use the product well. • Compensating for acknowledged issues. • Addressing specific complaints. Thursday, February 23, 12
- 27. Research questions Thursday, February 23, 12
- 28. Clear, succinct Thursday, February 23, 12
- 29. Measurable Quantifiable Thursday, February 23, 12
- 30. Don’t do this: Thursday, February 23, 12
- 31. Thursday, February 23, 12
- 32. • Is the product usable? Thursday, February 23, 12
- 33. • Is the product usable? • Is the product ready for release or does it need more work? Thursday, February 23, 12
- 34. Thursday, February 23, 12
- 35. • How easily do users understand what is clickable? Thursday, February 23, 12
- 36. • How easily do users understand what is clickable? • How easily do they find X information? Thursday, February 23, 12
- 37. • How easily do users understand what is clickable? • How easily do they find X information? • How quickly & successfully do they register for the service? Thursday, February 23, 12
- 38. • How easily do users understand what is clickable? • How easily do they find X information? • How quickly & successfully do they register for the service? • Where in the site do they go to find Search? Thursday, February 23, 12
- 39. Participant characteristics Thursday, February 23, 12
- 40. double-check with client Thursday, February 23, 12
- 41. # of participants Thursday, February 23, 12
- 42. Participant types Thursday, February 23, 12
- 43. Method (test design) Thursday, February 23, 12
- 44. Why? Thursday, February 23, 12
- 45. keeps everyone in the team on the same page Thursday, February 23, 12
- 46. multiple test moderators Thursday, February 23, 12
- 47. focuses test development Thursday, February 23, 12
- 49. Task list Thursday, February 23, 12
- 50. Thursday, February 23, 12
- 51. • Description of task (1 line) Thursday, February 23, 12
- 52. • Description of task (1 line) • Materials/Machine states required Thursday, February 23, 12
- 53. • Description of task (1 line) • Materials/Machine states required • Successful completion criteria Thursday, February 23, 12
- 54. • Description of task (1 line) • Materials/Machine states required • Successful completion criteria • Timing/Benchmarks Thursday, February 23, 12
- 55. Goal: Indirectly expose usability flaws Thursday, February 23, 12
- 56. Prioritize tasks: Frequency Criticality Vulnerability Readiness Thursday, February 23, 12
- 57. Test environment, equipment, and logistics Thursday, February 23, 12
- 58. Test moderator role Thursday, February 23, 12
- 59. Data to be collected Evaluation measures Thursday, February 23, 12
- 60. Report contents and presentation Thursday, February 23, 12