Test plan template
What to test, where the risk is and when testing is done.
- Stage
- Test
- Sections
- 6
- Updated
How to fill it in
- 1Say what is in scope, and what is not.
- 2Test the riskiest areas first.
- 3List the cases with their expected results.
- 4Agree the exit criteria up front.
Scope
What this plan covers, and what it deliberately leaves out.
Risks
- The riskiest areas first: new code, changed code, anything that touches money or data
Test cases
| Case | Steps | Expected | Result |
|---|---|---|---|
Environments
- Browser or device, version and test data
Exit criteria
The conditions that must be true before testing is called done.
- No must-fix bugs are open
- Every acceptance criterion has been checked
- The riskiest areas have been tested twice
Sign-off
Who agrees it is ready, and when.
What’s inside 6
- Scope
- Risks
- Test cases
- Environments
- Exit criteria
- Sign-off
Where to find it
In Kanso, add a page and pick this template, or type / in any doc.
Read the guide: A software launch checklist, step by step
Questions
A document that says what will be tested, where the risks are, how, in which environments and what must be true before testing is complete.
More templates
All templates
Use the test plan in Kanso.
Free does not expire. No card required.