Test plan vs test strategy
Updated 2026-11-13 · 2 min read
Compare test strategy decisions with release planning, including scope, risk, environments and exit criteria. Includes a comparison table, concrete examples and an interview answer.
The difference in one table
| Aspect | Test plan | Test strategy |
|---|---|---|
| Main question | How will we organise this testing work? | What testing approach addresses our risks? |
| Typical contents | Scope, people, dates, environments and criteria | Test levels, techniques, coverage and automation approach |
| Scope | Often a project, release or iteration | May be organisation-wide or specific to one product |
| Example decision | Who prepares payment data before execution? | Which payment risks need API and end-to-end checks? |
| Relationship | Can contain or refer to the strategy | Guides choices made concrete in the plan |
Examples
Strategy: for a checkout change, prioritise duplicate-payment and incorrect-total risks. Use focused API checks for calculation rules, contract checks at the payment boundary and a small set of end-to-end journeys. Explain why each layer is needed.
Plan: assign ownership, identify the sandbox and test data, schedule execution after integration is ready, and record entry and exit criteria. If the sandbox is unavailable, the plan identifies the blocker and what evidence remains missing.
These are example contents, not a mandatory document template. A small team may keep both in one short document.
How to answer in an interview
A test strategy explains the approach we choose to address product risks. A test plan organises a particular piece of testing, including scope, responsibilities, resources and completion criteria. For checkout, the strategy chooses layered coverage for payment risks, and the plan schedules those checks and names the required environment. Some teams combine both, so I describe the decisions rather than insist on two files.
Common confusion
Do not claim a strategy never changes or that only a manager can write it. New architecture or incident evidence can change the approach. A plan containing dates but no meaningful scope or criteria is also incomplete.
Likely follow-up: What changes when time is cut? Reassess risk, prioritise coverage and state the remaining gaps; shortening the calendar does not make the missing evidence disappear.
This is independent foundation-level learning material, not affiliated with ISTQB.
Quick answers
Is the strategy always an organisation-level document?
No. An organisation may define a policy or general approach while a product or project chooses a more specific strategy.
Can a sprint use a lightweight test plan?
Yes. A short shared record is useful if it makes scope, risks, responsibilities and completion evidence clear.
Sources
Want a project you can show in interviews?
The portfolio project kit walks you through testing a deliberately buggy app with Selenium or Playwright and API tests, then explaining it. The app itself is free.