Tech Talk


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Tech Talk

  1. 1. Usability Testing
  2. 2. <ul><li>Usability testing is a technique used to evaluate a product by testing it on users. This can be seen as an irreplaceable usability practise, since it gives direct input on how real users use the system. </li></ul>What is Usability Testing? Thanks Wikipedia! <ul><ul><li>Efficiency -- How long does it take people to complete basic tasks? (For example, find something to buy, create a new account, and order the item.) </li></ul></ul><ul><ul><li>Accuracy -- How many mistakes did people make? (And were they fatal or recoverable with the right information?) </li></ul></ul><ul><ul><li>Recall -- How much does the person remember afterwards or after periods of non-use? </li></ul></ul><ul><ul><li>Emotional response -- How does the person feel about the tasks completed? Is the person confident, stressed? Would the user recommend this system to a friend? </li></ul></ul>
  3. 3. <ul><ul><li>Think of what tasks we wanted focus our testing on. </li></ul></ul><ul><ul><li>Find a way to record the sessions so we can review and share the results with the rest of the team. </li></ul></ul><ul><ul><li>Fix the issues we find and retest to see if we need to refine them further. </li></ul></ul>So, How Do We Do This?
  4. 4. <ul><li>To do any kind of testing, you need test subjects. </li></ul><ul><ul><li>A LimeWire-wide email was sent out to request testers. </li></ul></ul><ul><ul><li>A schedule was created and confirmed with the respondants. </li></ul></ul><ul><ul><li>By the way, we're always interested in signing up more testers. </li></ul></ul>Call to Action
  5. 5. <ul><li>A trial run through the app was done by the tester and a script of the steps was created. </li></ul><ul><ul><li>Broken into five main sections, with an extra one prepared (just in case). </li></ul></ul><ul><ul><li>Sections had sub-tasks, such as &quot;Create a Site&quot;, &quot;Add an Event&quot;, etc. </li></ul></ul>The Script
  6. 6. <ul><li>Finally, testing began. </li></ul><ul><ul><li>The tester would give the user the main task to complete, but not go into detail. </li></ul></ul><ul><ul><li>Testing time was limited to 45 minutes a person. </li></ul></ul><ul><ul><li>Four users were tested in the course of the day. </li></ul></ul>The Test Sessions Session recorded with Screenflick
  7. 7. Postmortem <ul><li>We reviewed the test results and made plans on how to improve the UI. </li></ul><ul><ul><li>Each member chose the five most important issues they saw. </li></ul></ul><ul><ul><li>We reviewed the issues together and ranked them in order of importance. </li></ul></ul><ul><ul><li>Tasks and tickets were assigned. </li></ul></ul>
  8. 8. Fixing Targeted wireframes were created as needed to help focus the coding and graphic work. With tasks assigned, we moved to fix as many as we could before the next testing session.
  9. 9. <ul><li>A second round of testing was conducted. </li></ul><ul><ul><li>Handled the same way as the first test. </li></ul></ul><ul><ul><li>The tester focused primarily on seeing if the UI fixes have improved usability. </li></ul></ul><ul><ul><li>New issues were noted. </li></ul></ul>...and Repeat
  10. 10. Any Questions?