Download to read offline
Uploaded byKrista Kennedy
Usability Testing Plans
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.
More Related Content
![Performance Testing [not] somebody I used to know](https://cdn.slidesharecdn.com/ss_thumbnails/performancetestingsomebodythatiusedtoknow-130219212815-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Usability Testing Plans
- 1. Testing Plans: Mappingthe Work Thursday, February 23, 12
- 2. You got toknow where you want to go. Thursday, February 23, 12
- 3.
- 4. and you gotto know where the pitfalls are. Thursday, February 23, 12
- 5.
- 6. You need toknow Thursday, February 23, 12
- 7. • How • When • Where • Who • Why • What Thursday, February 23, 12
- 8. Worries: Formal? Casual? Thursday, February 23, 12
- 9.
- 10. Test plans also: Thursday,February 23, 12
- 11. Serve as maincommunication 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 theTest 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 youtesting? What’s the impetus? Thursday, February 23, 12
- 18. Reasons NOT totest: Thursday, February 23, 12
- 19.
- 20. • Improving userexperience Thursday, February 23, 12
- 21. • Improving userexperience • Everyone else is doing it Thursday, February 23, 12
- 22. • Improving userexperience • Everyone else is doing it • Space is available Thursday, February 23, 12
- 23. • Improving userexperience • Everyone else is doing it • Space is available • Somebody wants to do something shiny Thursday, February 23, 12
- 24. • Improving userexperience • Everyone else is doing it • Space is available • Somebody wants to do something shiny • Market testing Thursday, February 23, 12
- 25. Good reasons totest: Thursday, February 23, 12
- 26. • Understanding whichusers can use the product well. • Compensating for acknowledged issues. • Addressing specific complaints. Thursday, February 23, 12
- 27.
- 28.
- 29. Measurable Quantifiable Thursday, February 23, 12
- 30. Don’t do this: Thursday,February 23, 12
- 31.
- 32. • Is theproduct usable? Thursday, February 23, 12
- 33. • Is theproduct usable? • Is the product ready for release or does it need more work? Thursday, February 23, 12
- 34.
- 35. • How easilydo users understand what is clickable? Thursday, February 23, 12
- 36. • How easilydo users understand what is clickable? • How easily do they find X information? Thursday, February 23, 12
- 37. • How easilydo 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 easilydo 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.
- 43. Method (test design) Thursday,February 23, 12
- 44.
- 45. keeps everyone inthe 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
- 48.
- 49.
- 50.
- 51. • Description oftask (1 line) Thursday, February 23, 12
- 52. • Description oftask (1 line) • Materials/Machine states required Thursday, February 23, 12
- 53. • Description oftask (1 line) • Materials/Machine states required • Successful completion criteria Thursday, February 23, 12
- 54. • Description oftask (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 becollected Evaluation measures Thursday, February 23, 12
- 60. Report contents and presentation Thursday, February 23, 12