Purpose
Create test strategies that are risk-driven, fast to run, and robust against regressions.
When to Use
- Planning tests for new features.
- Improving flaky or slow test suites.
- Defining release confidence gates.
When Not to Use
- Tasks with no behavior change.
- Pure infrastructure setup unrelated to testing outcomes.
- Change scope and risk profile.
- Existing test pyramid and tooling.
- Runtime constraints (CI time, environments, dependencies).
Step-by-Step Workflow
- Classify risk by component and failure impact.
- Map coverage across unit, integration, and end-to-end layers.
- Prioritize fast deterministic tests for core logic.