# {App Name} v{Version} — QA Plan
*{One-line scope note — e.g. "New features only" or "Full pre-release pass"}*

---

**Before starting QA:**
- [ ] {Pre-flight item — e.g. "Confirm version shows X.X in About/Settings"}
- [ ] {Pre-flight item — e.g. "Have a writable test folder ready"}
- [ ] {Pre-flight item}

---

## SECTION 1 — {SECTION NAME, ALL CAPS}

| # | Test | Expected | Result | Notes |
|---|------|----------|--------|-------|
| 1.1 | {Action to take} | {What should happen} | | |
| 1.2 | {Action to take} | {What should happen} | | |
| 1.3 | {Action to take} | {What should happen} | | |

---

## SECTION 2 — {SECTION NAME, ALL CAPS}

| # | Test | Expected | Result | Notes |
|---|------|----------|--------|-------|
| 2.1 | {Action to take} | {What should happen} | | |
| 2.2 | {Action to take} | {What should happen} | | |

---

*{App Name} v{Version} — QA Plan*
*{Month Year}*

---

## FORMAT RULES (delete this section before importing — reference only)

- Title must be `# {App} v{Version} — QA Plan` — the H1 is parsed as the plan's display name.
- Pre-flight block must start with the exact line `**Before starting QA:**` followed by a `- [ ]` list. This becomes a separate pre-run checklist — checked/unchecked only, no pass/fail.
- Every section header must be `## SECTION N — TITLE`, ALL CAPS after the em dash. This drives section grouping and the collapse/expand navigation.
- Test IDs must be `{section}.{item}` (e.g. `1.1`, `1.2`, `2.1`) — sequential within each section, restarting at `.1` for each new section.
- Table columns must stay in this exact order: `# | Test | Expected | Result | Notes`. Leave Result and Notes empty — the app fills those in during a run.
- Keep test rows atomic: one observable action, one observable expected outcome per row. If a test needs multiple steps, number them within the "Test" cell rather than splitting into ambiguous separate rows.
- No nested tables, no merged cells, no HTML — plain Markdown tables only.