The practical distinction
Test Strategy: How will quality be validated?
Test Plan: What testing will actually be performed for this delivery?
Test Plan: What testing will actually be performed for this delivery?
This distinction separates the governing approach from execution-level planning.
What belongs in a test strategy
- Quality objectives
- Scope/exclusions
- Risk model
- Test levels/types
- Environment strategy
- Test data approach
- Automation approach
- Entry/exit criteria
- Roles/governance
- Evidence/reporting
What belongs in a test plan
- Features/stories in scope
- Specific test suites
- Schedule/milestones
- Assigned resources
- Environment dates
- Test data preparation
- Execution sequence
- Dependencies
- Defect/retest cycles
- Release-specific exit status
Comparison
| Question | Strategy | Plan |
|---|---|---|
| Purpose | Define the quality approach | Organize execution |
| Level | Governing | Delivery-specific |
| Change frequency | Relatively stable | Changes with delivery |
| Risk | Explains how risk drives validation | Shows activities addressing current risk |
Do you need two documents?
Not always. A small change may be served by one concise page. A major program may need a strategy plus release-specific plans.
Good strategy documents contain decisions. If a document only contains generic testing definitions, it is not yet a useful strategy.