test-planning-process
Installation
SKILL.md
Test Planning Process
Quick Reference
| Dimension | Rule |
|---|---|
| Test Boundary | Test at the highest boundary that directly expresses the feature's business goal (e.g. integration/request vs unit) |
| Coverage Goal | Cover all primary paths, all input boundary values, and all expected error flows |
| First Failing Test | Select the single simplest assertion that will fail on the current code and prove the feature is missing |
| Isolation | Isolate tests from external networks, dates, and shared database states |
HARD-GATE
TEST PLANNING GATES:
1. DO NOT write test cases without defining a test plan first.
2. ALWAYS start testing at the most relevant boundary (don't write 10 unit tests for a feature that needs a request test, and vice versa).
3. The first failing test MUST be identified explicitly in the plan before writing it.
4. All test data must be synthetic; never use real production values or API payloads in test plans.