test-planlisted
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# Test Plan
The document that exists between the working agreement (how we work) and the
test report (what happened). Teams skip it, then argue at the end of the release
about whether something was in scope.
Keep it short. A test plan nobody reads has the same value as no test plan, and
length is the main reason they go unread. Two pages for a release, half a page
for an epic.
## Structure
```markdown
# Test plan — Platform release 2.4
**Scope** Confluence integration, bulk export, login rework (PLAT-118, 112, 104)
**Period** 9–20 September 2026 · **Prepared by** Alex T. · **v1.1**
## Approach by layer
| Layer | Approach | Owner |
|---|---|---|
| API | Automated, Playwright, per requirement | QA, automated |
| UI | Automated for core paths, manual for states and accessibility | QA |
| Database | State assertions where the API does not expose the outcome | QA |
| Integration | Contract tests between admin and item-service | QA + backend |
| Performance | Load at expected peak after functional sign-off | QA |
| Security | Authorisation boundaries and OWASP API classes | QA |
| Exploratory | Four charters, one per risk area | QA |
## Not in scope
- Mobile clients — no QA coverage this release, owned by the mobile team
- Load above 50 concurrent users — no requirement stated
- Penetration testing — out of scope for QA; no external engagement booked
## Environments and data
Staging, shared with the backend team. Deploys at 09:00 daily — do not test then.
Test accounts: sup