01 / Requirements
Write requirements a team can test
A useful requirement names the user, the expected behavior, and the conditions that make the work complete.
01State the outcome
Describe who needs the change and what they should be able to do. Keep implementation choices separate from the user outcome.
02Make acceptance criteria observable
Write conditions a reviewer can check, including the expected result for valid, invalid, and boundary inputs.
03Review before test design
Ask product, engineering, and QA to resolve ambiguous terms and missing rules while the requirement is still easy to change.
Review checklist
- A named user or business need
- Observable acceptance criteria
- Known exceptions and boundaries
- An owner and review status
02 / Test design
Design test cases that explain the risk
Good test cases make the purpose, setup, action, and expected result clear enough for another person to execute.
01Start from a criterion
Link each case to the requirement or acceptance criterion it checks so the reason for the test remains visible.
02Cover more than the happy path
Include negative, boundary, permission, and recovery scenarios where they matter to the user or release.
03Keep cases reviewable
Use concise steps and one clear expected result per check. Review generated cases before adding them to a plan.
Review checklist
- Source requirement
- Preconditions and test data
- Action and expected result
- Priority or risk addressed
03 / Traceability
Follow a requirement through testing
Traceability lets a team explain how product intent was reviewed, tested, and reflected in results and defects.
01Connect the artifacts
Keep the requirement, test case, plan, execution result, and related defect linked where possible.
02Look for gaps
Check for approved requirements without tests and planned tests without a clear requirement or purpose.
03Use the links in review
When a test fails, move back to the source criterion. When a requirement changes, identify the cases that need another look.
Review checklist
- Requirement to case
- Case to plan and run
- Result to defect when needed
- Coverage gaps reviewed
04 / Risk
Focus testing where failure matters most
Risk-based testing helps teams decide where to spend limited review and execution time.
01Estimate impact
Consider user harm, business interruption, security, data integrity, and operational consequences if a behavior fails.
02Consider likelihood
Look at complexity, recent changes, dependencies, and past defects rather than treating every requirement as equally uncertain.
03Review the priority
Use risk to guide test depth and sequencing, then revisit the priority as evidence changes.
Review checklist
- Impact stated
- Likelihood considered
- High-risk areas tested first
- Remaining risk visible
05 / Release readiness
Make a release decision with evidence
A readiness conversation should show what was planned, what ran, what failed, and what risk remains.
01Compare plan and progress
Confirm the intended test scope, execution status, and any work that was deferred or not run.
02Review open issues
Look at severity, ownership, and the user-facing impact of unresolved defects rather than counting issues alone.
03Record the decision
Summarize the evidence, known gaps, owners, and follow-up actions so the reason for the decision is clear later.
Review checklist
- Scope and execution progress
- High-risk requirements
- Open severe defects
- Known gaps and decision owner