ConceptsIntermediate4-6 min reference
Usability Heuristics for QA
Usability bugs rarely have a failing assertion — the feature "works" but frustrates. Nielsen's 10 heuristics give QA a vocabulary to spot and report them credibly. This sheet reframes each as a question to ask while testing. It pairs with Exploratory Testing Heuristics and the accessibility sheets linked below.
The 10 heuristics (as QA questions)
| # | Heuristic | Ask while testing |
|---|---|---|
| 1 | Visibility of system status | Does the UI show what's happening (loading, saved, progress)? |
| 2 | Match to the real world | Is the language the user's, not the system's/jargon? |
| 3 | User control & freedom | Is there a clear undo / cancel / back / exit? |
| 4 | Consistency & standards | Do the same things look and behave the same way? |
| 5 | Error prevention | Are mistakes prevented (confirmations, constraints) before they happen? |
| 6 | Recognition over recall | Are options visible, not something the user must remember? |
| 7 | Flexibility & efficiency | Are there shortcuts for power users without blocking novices? |
| 8 | Aesthetic & minimalist | Is the screen free of competing, irrelevant clutter? |
| 9 | Help users with errors | Are errors plain-language, specific, and do they suggest a fix? |
| 10 | Help & documentation | Is help available and findable at the point of need? |
How to use it
Run a screen against the 10 questions during exploratory testing. Each "no" is a usability finding — log it with the heuristic name and a screenshot so it lands as a credible report, not an opinion.
Common mistakes
- Reporting "this is confusing" with no heuristic or evidence — easy to dismiss.
- Treating usability issues as out of scope for QA (you're the first real user).
- Confusing usability with accessibility — related, but test both (see the a11y sheets).
- Logging severity as trivial by default; a confusing checkout is a revenue bug.
// Related resources