Where the test strategy sets the direction for the whole product, the test plan organises one specific campaign: a version, a feature, a migration.
What’s in the kit
- Identification of the version under test.
- The campaign’s goal.
- Features to test, with their priority.
- Features not tested, and why.
- Approach: automated, manual, exploratory, non-functional.
- A ready-to-fill test case table, with status.
- Environment and data.
- The campaign schedule.
- Exit criteria as a checklist.
- Risks and fallback plans.
- A summary with figures and the go / no-go decision.
How to use it
Duplicate the template for each campaign. Start with the feature table and its priorities: that’s what decides how much time goes into each test case. The final summary is your record of the go-live decision.



