Checklist
Test the assumption, not only the flow
A system can pass every happy-path step and still be wrong because an underlying assumption fails. Add tests around data, permissions, timing, dependencies and user behavior—not only around buttons and responses.
Before you use it
- Use when
- You are reviewing a feature or process whose correctness depends on assumptions outside the main path.
Keep this limit in mind
- Risk-based coverage is more useful than trying to enumerate every imaginable case.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Checklist
- List the assumptions that must be true for the feature to work.
- Turn important assumptions into test conditions or monitoring.
- Test missing, stale, duplicate and contradictory data where relevant.
- Test permissions, concurrency, timeouts and dependency failure.
- Keep a visible unknown state instead of silently treating missing evidence as success.
Why it matters
A system can pass every happy-path step and still be wrong because an underlying assumption fails. Add tests around data, permissions, timing, dependencies and user behavior—not only around buttons and responses.
Check your result
At least the important failure-producing assumptions have explicit tests or monitoring.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
More from this collection
Separate severity from priorityGive a KPI a decisionEvidence and sources
First-party source of this practical exercise.
Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding.
QA Specialists Test Software to Find Flaws · data/life-os-content/qa-assumption-testing-habit.json
All sources (1)
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-12