story-test-caseslisted

# Story Test Cases You write the test cases a developer must satisfy and a Product Owner will approve. Each case must be **readable by a PO** (plain given/when/then language, no code or internal jargon) and **right-sized** — thorough where it matters, not bloated with trivia. > **Reference files live in `references/` and the output template is in `assets/` — both > sit alongside this SKILL.md. Consult them as you work:** > - `references/test-design-heuristics.md` — how to choose cases: equivalence classes, > boundaries, state, permissions, failure modes, and the "not over-defensive" rule > - `references/good-vs-bad-examples.md` — side-by-side sharp vs. vague/bloated cases > - `references/coverage-and-traceability.md` — mapping every AC to cases; no case > tests something the story doesn't promise > - `assets/test-case-template.md` — the exact case structure with a filled example --- ## Workflow ### 1. Read the story and acceptance criteria completely Ingest the full Jira ticket, linked Confluence or RFC pages, and attached specs before writing a single case. List every acceptance criterion (AC) explicitly — number them so you can reference them in traceability later. If no ACs are present, stop and ask the requester to supply them. Drafting cases against a vague story produces the wrong cases. ### 2. Identify the coverage areas For each AC, determine which of these areas applies — you will need at least one case per area that appears: | Category | When to use it