What it does
The single-case fast path: treats the description as the test basis for one condition, picks the cheapest effective level and exactly one CTFL v4.0 design technique, places the test in an existing spec where possible, writes it, and runs just that test.
When to use it
One-off 'add a test that...' requests for a single behavior.
Prerequisites
qa.config.yml (run /qa:qa-init first) and a test framework (run /qa:scaffold if none); honors tooling.*, paths.tests_dir, stack.api_spec_path, test_data.*, risk_areas.
Output
One implemented and run test procedure/script added under paths.tests_dir (29119-3 Test Procedure Specification).
Mechanics
How it works
- Resolve the condition from arguments (default to the first risk_areas.critical item if empty)
- Pick the cheapest effective test level for what is being verified
- Select exactly one CTFL v4.0 Chapter 4 technique via the decision tree and record it
- Place the test in an existing spec covering the same feature/level; only create a new file if none fits
- Write the test with stable selectors, web-first assertions, no hard waits, owning its data, and a trace comment
- Run just this test; fix it if it is the test's fault, or escalate to /qa:triage if it is a real defect
Why it works
The theory behind it
Test design + implementation (CTFL v4.0 §1.4, §4) compressed to one case — the quick path; test-cases (design) and implement (multi-level) are the full-suite paths.
CTFL v4.0 §1.4 · §4
Example
See it in use
> /qa:add-test "password reset link expires after 30 minutes"✓ Correct when It adds a single self-validating test with real assertions that owns its data and names the one technique used.
Related commands
Used by