Test Plan: Feature / release name
QA plan – strategy matrix, cases, entry/exit criteria
Cara menggunakan: Release cycles, regulated environments, QA sign-off. Entry/exit criteria prevent "we tested it, kind of".
Pratinjau
Test Plan: Feature / release name
| Field | Value |
|---|---|
| Version | X.Y |
| Author | @qa |
| Date | YYYY-MM-DD |
| Status | Draft / Active / Complete |
Scope
In scope: features/areas tested in this cycle. Out of scope: what is not covered and why.
Test strategy
| Level | Approach | Tools |
|---|---|---|
| Unit | Automated | vitest |
| Integration | Automated | playwright |
| E2E | Automated + exploratory | playwright |
| A11y | Automated | axe |
| Performance | Manual + budget | lighthouse |
Environment
- OS / browsers / devices matrix
- Test data setup
Test cases
| ID | Title | Steps summary | Expected | Priority | Result |
|---|---|---|---|---|---|
| TC-01 | Login with valid credentials | ... | Redirect to dashboard | P0 | Pass/Fail |
| TC-02 | Export large doc | ... | PDF generated <10s | P1 | |
| TC-03 | Offline reload | ... | Docs still available | P0 |
Entry criteria
- Build deployable, smoke test passes
- Test data prepared
- Requirements frozen for this cycle
Exit criteria
- 100% P0 cases executed, all passing
- No open critical/blocker defects
- Regression suite green
Risks
| Risk | Impact | Mitigation |
|---|---|---|
| Flaky env | Missed coverage | Retry protocol |
Defect log
| ID | Summary | Severity | Status |
|---|---|---|---|
| BUG-1 | ... | Critical | Open |