2 / 62 · 22 Test Strategy & Quality Metrics · Building a Test Strategy← prev⊞ allnext →☰ Read as one page
1.2Test Strategy vs Test Plan
| Dimension | Test Strategy | Test Plan |
|---|---|---|
| Scope | Entire product or program | Single release, feature, or sprint |
| Timeframe | Long-term (6-12+ months) | Short-term (1 sprint to 1 release) |
| Author | QA Lead / QA Architect | QA Engineer on the feature |
| Audience | Engineering leadership, stakeholders | Development team, QA team |
| Content | Approach, tools, risk tolerance, principles | Specific test cases, schedule, assignments |
| Change frequency | Quarterly or when major product changes occur | Every sprint or release |
| Question answered | "How do we approach quality for this product?" | "What are we testing this sprint and when?" |
Analogy: A test strategy is a military campaign plan (where to fight, what resources to deploy, what the objectives are). A test plan is a battle plan (specific troop movements, timing, terrain analysis for one engagement).