How do you create a test strategy document for a new project?
- test strategy
- planning
- documentation
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Key sections: (1) Scope: what is being tested and what is explicitly out of scope. (2) Test levels: unit, integration, e2e, performance, security. (3) Test types per feature: functional, non-functional, regression. (4) Environment strategy: where each test level runs. (5) Tools and frameworks: with justification for each choice. (6) Entry/exit criteria: when testing starts and when we are done. (7) Risk assessment: highest-risk areas and mitigation strategy. (8) Roles and responsibilities: who writes which tests. (9) Schedule and milestones. (10) Defect management process. Keep it living: update it each sprint, not a shelf document.
What interviewers listen for
- Risk-based prioritisationYou can defend skipping coverage on a path because the risk maths supports it.
- Test design fluencyYou apply equivalence partitioning and decision tables to concrete inputs in real time.
- Metric judgmentYou distinguish between metrics that drive learning and metrics that drive theatre.
- Strategy under constraintYou can produce a defensible plan when the team has half the time and twice the scope.