UX (Planning for Front-End User Testing (Why? (Additional clarity on scope…
Planning for Front-End User Testing
Additional clarity on scope (e.g. supported browsers and devices)
Less explaining (and argument) later with the client
Less stress before, during and after launch
You cannot test everything, be realistic!
Budgets are finite
Schedules are finite
Not every scenario matters
Creating a test plan
Identify who you're testing for
What are the most popular devices they'll use?
What OS/browser combinations are most popular among audience?
What connection speeds do they have?
How tech-savvy is your demographic?
Use statistical information available online
Net Market Share
Prioritize browser & device support
Fully supported browsers & devices
Partially supported browsers & devices (degradation in the UI cannot obscure content)
Unsupported browsers & devices
Decide what to test
WC3 Markup Validation Service
Google Webmaster Tools
Videotaped user sessions
Surveys (Survey Monkey)
Ease and effectiveness of navigation
Usefulness of content
Effectiveness of visual presentation (UI)
Errors & Exceptions
Web Load Testing
Web Stress Testing
3 things to know upfront
what's worth doing?
what are we creating?
what value does it provide?
3 kinds on requirements
things people say they need
things people actually need
things people don't know they need
the most important principle of good UI/UX is
who's the competition?
use scenarios to get requirements quickly
documentation eliminates excuses and surprises
write it down
be realistic about what matters most
when interacting with clients or partners
silence equals agreement