| name | Test Strategy |
| description | Use when adding features, fixing bugs, preparing release, refactoring, or when confidence matters. Designs and runs minimal high-value tests without wasting time. |
| allowed-tools | Read, Bash, Edit, MultiEdit, Write |
Test Strategy
Use this skill to get confidence with minimal test cost.
Test Selection
- Start with nearest existing test pattern.
- Cover changed behavior first, not implementation details.
- Add one regression test for the bug when possible.
- Prefer small deterministic tests over broad brittle suites.
- Run targeted tests before full suite.
- Check impacted parent flow, adjacent state, and likely caller/component.
- If tests cannot run, state exact blocker and safest manual verification.
Coverage Targets
- Core success path.
- Failure path likely to break.
- Boundary values.
- Auth/permission edge when security relevant.
- UI state: loading, empty, error, success.
- API state: validation failure, auth failure, provider failure, retry/idempotency when relevant.
- Diff review: accidental behavior change, duplicated logic, hidden weakening.
Final Verification
Report:
- Commands run.
- Passed/failed.
- Coverage gap.
- Residual risk.