What it does
Runs the ISTQB analysis-to-design flow: derives test conditions, picks the right technique per condition (EP, BVA, decision table, state transition, experience-based, ATDD), and writes a Test Case Specification with risk-based priority and detail plus a coverage summary.
When to use it
Whenever you need to create or derive concrete test cases for an item.
Prerequisites
qa.config.yml (risk_areas tiers map to priority; paths.docs_dir is the write target); a requirement/story/endpoint/file, or empty to default to the first risk_areas.critical item.
Output
ISO/IEC/IEEE 29119-3 Test Case Specification -> docs/TEST-CASES-<item>.md (+ optional CSV export).
Mechanics
How it works
- Test analysis: derive test conditions, tag each with a risk level, flag basis gaps
- Technique selection: pick the right CTFL v4.0 Ch.4 technique per condition
- Test design: write atomic, independent cases covering positive, negative, boundary, error and authorization paths
- Map each case's risk tier to priority (critical->P1 … low->P3) and set risk-based detail level
- Quality checks for atomicity, coverage, traceability; run self-check; write the spec + coverage summary
Why it works
The theory behind it
Test analysis -> design (CTFL v4.0 §1.4, §4) using EP, BVA, decision tables and state transition — how you sample the infinite input space well (Principle 2) and aim where defects cluster (Principle 4, boundaries). Pairwise/use-case are labeled Advanced (CTAL-TA), never Foundation.
CTFL v4.0 §1.4 · §4 · CTAL-TA (Advanced techniques)
Example
See it in use
> /qa:test-cases "As a guest I can check out with a saved card"✓ Correct when Each case names its technique (EP/BVA/decision table) and includes negative and boundary cases, not just the happy path; output is a Test Case Specification at docs/qa/.
Related commands
Used by