#@ QA Checklist Template
Copy this file when starting a new module's QA checklist. Replace the placeholders, keep the section order, and follow the rules in Testing & QA overview.
Each Critical and High item carries a VitePress status badge in its title:
<Badge type="tip" text="covered" />— a unit/integration test asserts the exact behaviour.<Badge type="warning" text="partial" />— related assertions exist, but the risk is not fully closed.<Badge type="danger" text="not implemented" />— no automation yet; QA must test manually.
Flip the badge in the same PR that changes behaviour or tests.
# <Module Area> — QA Test Plan
Pre-release checklist grounded in the current code. One-line statement about why this module needs extra care (e.g. "money-handling module", "irreversible action", "customer-facing").
Totals
| Severity | Count |
|---|---|
| Critical | 0 |
| High | 0 |
| Medium | 0 |
| Low | 0 |
| Total | 0 |
Coverage summary (Critical + High)
000
Critical — Release blockers
C1 — <Short, specific title>
Scope: <One-line statement of the invariant under test.>
Tests:
<path/to/test.ts>→<describe name>(omit when not implemented)
Steps:
<…><…>
Expected: <What a passing run looks like.>
Risk: <What breaks if this ships — user / revenue / data POV.>
Ref: <src/... source file — optional, one line max.>
C2 — <…>
(repeat the same block)
High — Core flows
H1 — <…>
(repeat)
Medium — Edge cases and UX gaps
M1 — <…>
Scope: <One-line description.>
Steps: <Short manual steps — no full template needed.>
Risk: <One line.>
Ref: <src/... source file — optional.>
Low — Polish and cleanup
L1 — <…>
Scope: <One line.>
Ref: <src/... source file — optional.>
Unit tests worth adding next
| ID | Title | Where |
|---|---|---|
C1 |
<What to assert> |
<src/__tests__/... path> (new) |
C2 / C3 |
<…> |
<…> |
Out of scope
One short paragraph listing concerns that do not live in this module.
Retired items (optional)
Move obsolete IDs here with a one-line note on why. Never delete historical IDs.