1.5Template: The One-Page Sprint Test Plan

For most sprint-level testing, a one-page plan is sufficient and far more likely to be read than a multi-page document.

# Test Plan: [Feature Name] -- Sprint [N]

## Scope
What is being tested. What user stories are covered.

## Out of Scope
What is explicitly not being tested and why.

## Approach
- Manual testing: [what and why]
- Automated testing: [what and why]
- Exploratory testing: [focus areas]

## Test Environments
| Environment | URL | Purpose |
|---|---|---|
| Staging | staging.example.com | Integration and regression |
| QA | qa.example.com | Feature testing |

## Test Data
What test data is needed and how to obtain it.

## Risks
| Risk | Impact | Mitigation |
|---|---|---|
| Payment API sandbox may be unavailable | Cannot test checkout | Use mock service |
| New design system may break existing flows | Visual regressions | Run visual regression suite |

## Entry Criteria
- [ ] Feature code deployed to staging
- [ ] Test data loaded
- [ ] Test environments accessible

## Exit Criteria
- [ ] All critical test cases passed
- [ ] No open Sev-1 or Sev-2 bugs
- [ ] Automation suite green
- [ ] Exploratory testing completed

## Schedule
| Activity | Start | End | Owner |
|---|---|---|---|
| Test case design | Mon | Tue | QA team |
| Manual execution | Wed | Thu | QA team |
| Automation updates | Wed | Fri | SDET |
| Exploratory testing | Thu | Fri | Senior QA |