---
name: Test Planning
description: Plan testing before executing it.
---
# Test Planning

A test plan defines what will be tested, how, and against what criteria — before execution. Without it, testing becomes ad-hoc, gaps go unnoticed, and "are we done?" has no answer.

## Contents
- **Scope.** What's in test (features, platforms, integrations) and explicitly out.
- **Strategy.** Unit, integration, e2e, exploratory, performance, security — which apply, and the ratio.
- **Entry/exit criteria.** When does testing start (build stable)? When does it end (defects below threshold, critical paths green)?
- **Environment & data.** What config, what test data, what stubs.
- **Risk-based focus.** Spend the most testing effort where risk is highest (new code, complex logic, high-impact paths).

## Use
The plan is a contract with the team about what "tested" means. Update it as you learn; a stale plan is fiction.