Usability Testing Plans

of 60 /60
Testing Plans: Mapping the Work Thursday, February 23, 12

Embed Size (px)

Transcript of Usability Testing Plans

  • 1.Testing Plans: Mapping the WorkThursday, February 23, 12

2. You got to know whereyou 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 knowThursday, February 23, 12 7. How When Where Who Why WhatThursday, February 23, 12 8. Worries:Formal?Casual?Thursday, February 23, 12 9. Prepared.Thursday, February 23, 12 10. Test plans also:Thursday, February 23, 12 11. Serve as main communication vehicleThursday, February 23, 12 12. Denes requiredresources.Thursday, February 23, 12 13. DeneFocal pointsMilestonesThursday, February 23, 12 14. Parts of the Test PlanThursday, February 23, 12 15. Purpose, goals, andobjectives of the testThursday, February 23, 12 16. Broadly.Major stuff.Thursday, February 23, 12 17. Why are you testing?Whats the impetus?Thursday, February 23, 12 18. Reasons NOT to test:Thursday, February 23, 12 19. Thursday, February 23, 12 20. Improving user experienceThursday, February 23, 12 21. Improving user experience Everyone else is doing itThursday, February 23, 12 22. Improving user experience Everyone else is doing it Space is availableThursday, February 23, 12 23. Improving user experience Everyone else is doing it Space is available Somebody wants to do something shinyThursday, February 23, 12 24. Improving user experience Everyone else is doing it Space is available Somebody wants to do something shiny Market testingThursday, February 23, 12 25. Good reasons to test:Thursday, February 23, 12 26. Understanding which users can use theproduct well. Compensating for acknowledged issues. Addressing specic complaints.Thursday, February 23, 12 27. Research questionsThursday, February 23, 12 28. Clear, succinctThursday, February 23, 12 29. MeasurableQuantiableThursday, February 23, 12 30. Dont 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 itneed more work?Thursday, February 23, 12 34. Thursday, February 23, 12 35. How easily do users understand what isclickable?Thursday, February 23, 12 36. How easily do users understand what isclickable? How easily do they nd X information?Thursday, February 23, 12 37. How easily do users understand what isclickable? How easily do they nd X information? How quickly & successfully do they registerfor the service?Thursday, February 23, 12 38. How easily do users understand what isclickable? How easily do they nd X information? How quickly & successfully do they registerfor the service? Where in the site do they go to ndSearch?Thursday, February 23, 12 39. ParticipantcharacteristicsThursday, February 23, 12 40. double-check with clientThursday, February 23, 12 41. # of participantsThursday, February 23, 12 42. Participant typesThursday, 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 pageThursday, February 23, 12 46. multiple testmoderatorsThursday, February 23, 12 47. focuses testdevelopmentThursday, February 23, 12 48. protocolsThursday, February 23, 12 49. Task listThursday, 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 requiredThursday, February 23, 12 53. Description of task (1 line) Materials/Machine states required Successful completion criteriaThursday, February 23, 12 54. Description of task (1 line) Materials/Machine states required Successful completion criteria Timing/BenchmarksThursday, February 23, 12 55. Goal: Indirectly expose usability awsThursday, February 23, 12 56. Prioritize tasks:FrequencyCriticalityVulnerabilityReadinessThursday, February 23, 12 57. Test environment,equipment, and logisticsThursday, February 23, 12 58. Test moderator roleThursday, February 23, 12 59. Data to be collectedEvaluation measuresThursday, February 23, 12 60. Report contents and presentationThursday, February 23, 12