Test Plan — [Feature / Release Name]
| Version / build | |
| Author | |
| Date | |
| Reviewers / sign-off | PM: · Eng lead: |
1. Objective
One paragraph: what is being released and what quality question this plan answers.
2. Scope
In scope:
Out of scope (and why):
3. Test approach
Which techniques where — e.g., EP/BVA on all input forms, decision table for pricing rules, exploratory charters on new flows, regression suite R-12 on touched modules, API checks on changed endpoints.
4. Environments & devices
| Environment | URL / build | Notes |
|---|---|---|
| Staging | ||
| Browsers | e.g. Chrome/Firefox/Safari latest, per traffic analytics | |
| Devices |
5. Test data & accounts
Seeded accounts, payment sandbox cards, feature flags needed.
6. Entry criteria
- Build deployed to staging
- Smoke suite passing
- Blockers from previous cycle verified fixed
7. Exit criteria
- 100% P1 cases executed
- ≥ __% overall pass rate
- No open critical/high defects
- Known issues documented and signed off
8. Schedule & people
| Activity | Owner | Dates |
|---|---|---|
| Case design | ||
| Execution round 1 | ||
| Retest & regression | ||
| Summary report |
9. Risks & mitigations
| Risk | Impact | Mitigation |
|---|---|---|
10. Deliverables
Test cases (link) · Bug reports (filter link) · Test summary report