| name | test-strategy |
| description | Design a risk-based test strategy that maps product and technical risks to appropriate validation layers and release evidence. |
Test Strategy
Use for significant features, releases, migrations, or changes where ad hoc testing is insufficient.
Procedure
- Identify critical user outcomes, system invariants, failure consequences, and changed surfaces.
- Rank risks by likelihood and impact.
- Map each risk to the cheapest reliable validation layer: static checks, unit, integration, contract, E2E, performance, security, exploratory, or manual operational proof.
- Define environments, data, fixtures, and observability required to make failures diagnosable.
- Specify entry/exit criteria and the evidence required for release confidence.
- Avoid duplicate tests that prove the same thing at more expensive layers unless defense in depth is justified.
- Update the strategy when defects reveal unmodeled risk.
Quality gate
The strategy must explain what can break, how it will be detected, and why the chosen tests are sufficient.