Checklist-Based Testing
Structured lists of what to verify — built from experience, standards, and known failure modes. More flexible than formal test cases; more structured than ad hoc testing.
What it is
A checklist is a list of conditions, questions, or items to verify. Unlike formal test cases, checklists don’t specify exact steps or expected results — they specify what to check, leaving the tester to determine how.
This flexibility makes checklists valuable when testing requires judgment (accessibility, UX quality, cross-browser compatibility) or when the exact steps can’t be scripted in advance.
Example checklists
| # | Check |
|---|---|
| 1 | Required fields marked with visible indicator |
| 2 | Required fields validated on submit — not mid-typing |
| 3 | Error messages are specific ("Enter a valid email address") not generic ("Invalid input") |
| 4 | Valid data accepted, form submits successfully |
| 5 | Field length limits enforced and communicated to user |
| 6 | Tab order follows visual layout, logical sequence |
| 7 | All labels correctly associated with their inputs |
| 8 | Successful submission provides clear confirmation |
| # | Check |
|---|---|
| 1 | Layout intact on Chrome, Firefox, Safari, Edge |
| 2 | No horizontal scroll on mobile (320px – 768px) |
| 3 | Touch targets ≥ 44px on mobile |
| 4 | Images load and aren’t stretched or cropped unexpectedly |
| 5 | Fonts render correctly — no invisible or fallback text |
| 6 | Navigation works at all breakpoints |
Maintaining checklists
A checklist is a living document. Every time you find a bug that wasn’t on the list, add it. When an item becomes irrelevant or is now covered by automation, remove it. Review and prune checklists at least once per release cycle.
At senior level, you should own and maintain checklists for your area. At lead level, you’ll have team-wide checklists that become the baseline quality standard.
Checklists vs formal test cases
- Checklists are faster to create and maintain. Good for experienced testers who know how to check the thing.
- Formal test cases are more precise. Required when tests will be re-run by different people, when compliance evidence is needed, or when automated.
- Many teams use checklists for exploratory and regression testing, and formal test cases for critical paths and audit trails.
ISTQB mapping
| Ref | Topic |
|---|---|
| 4.4.2 | Checklist-Based Testing — high-level conditions, structured but flexible |
| 4.4.2 | Checklists derived from experience, standards, requirements, and defect data |
Practice this technique: Try Grad Practice 07 — Team & about page, Senior Practice 01 — Accessibility audit.
Try It — Checklist or formal test case?
For each testing scenario below, decide whether a checklist or a formal test case is the more appropriate tool.
| Scenario | Your choice |
|---|---|
| Verifying that a payment gateway integration charges the correct amount to the cent — evidence required for financial audit | |
| Quickly checking that a refreshed marketing landing page looks right across 4 browsers before go-live | |
| Confirming a bug fix for a specific edge case — needs to be re-run by another tester in a different timezone | |
| General accessibility review of a new feature — checking WCAG criteria with judgment calls required | |
| Testing a government portal's identity verification flow that must comply with NZ Digital Service Design Standards |
Answers
| Scenario | Best tool | Why |
|---|---|---|
| Payment gateway audit | Formal test case | Exact steps, precise expected results, traceable audit evidence required. |
| Marketing page cross-browser check | Checklist | Experienced tester knows how to check; judgment-based; no exact steps needed. |
| Bug fix re-run by different tester | Formal test case | Reproducible across testers and time zones requires precise steps. |
| Accessibility review | Checklist | WCAG criteria map naturally to checklist items; requires tester judgment throughout. |
| Government identity verification | Formal test case | Compliance requirement — traceability to NZ standards and audit trail needed. |
The key decision factor: does someone else need to replicate this exactly, or produce audit evidence? If yes, formal test case. If it’s a judgment-based check by an experienced tester, a checklist is faster and just as effective.