ARTDM 171, Week 17: Usability Testing and QA


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

  • Usability is a quality attribute that assesses how easy user interfaces are to use.

  • ARTDM 171, Week 17: Usability Testing and QA

    1. 1. ARTDM 171, Week 17: Usability Testing and QA Gilbert Guerrero
    2. 2. Screenshot Add a screenshot to the blog
    3. 3. Usability Testing
    4. 4. Definition • Usability is defined by five quality components: ‣ Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design? ‣ Efficiency: Once users have learned the design, how quickly can they perform tasks? ‣ Memorability: When users return after a period of not using it, how easily can they reestablish proficiency? ‣ Errors: How many errors do users make, how severe, and how easily can they recover? ‣ Satisfaction: How pleasant is it to use the design? •  From Usability 101: Introduction to Usability, Jakob Nielsen
    5. 5. Usability Testing • Find users from the audience your site is intended to serve • Create a list of tasks for users to perform on your site • Observe them as they perform the tasks • Ask them speak aloud about their choices or when they don't understand something
    6. 6. Keep These in Mind • Do not help your test users or tell them where to click. • Remind them that you are not testing them–the site is what's being tested.  There's no wrong way to perform the tasks. • You can test your site with as little as five people.  As soon as you start seeing a pattern, you've probably discovered an issue that you can revise and test again. First Rule of Usability? Donʼt Listen to Users by Jakob Nielsen
    7. 7. Usability Testing Grab a partner
    8. 8. Quality Assurance Testing  
    9. 9. Quality Assurance • Before delivering a final site to your audience, you'll want to make sure that it all works • Important: Test that it doesn't do anything you didn't intend • Sometimes called Bug Testing
    10. 10. QA Checklist • Operating Systems (Mac, PC, Linux) • Browsers (Firefox, IE6, IE7, Safari, Chrome) • Links • Spelling • Functionality (forms, menus)
    11. 11. QA Resources • Browser Archive - http://   • W3C Markup Validation Service - http://
    12. 12. Resource Web Redesign 2.0: Workflow That Works by Kelly Goto and Emily Cotler
    13. 13. Homework • Post a screenshot of your website on the blog and a sentence about it • Conduct usability testing on your final project with 5 users • Make revisions
    14. 14. Thank You