Cursor rule

1---
2description: "Design a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles."
3alwaysApply: false
4---
5 
6# Plan Tests
7 
8> **Spine position:** Between `slice-tasks` and `plan-work` for epics with `risk: P0|P1`. Optional (can be waived in `state.yaml`) for P2/P3.
9 
10Bridges the gap between slicing and planning by systematically designing the test suite as a first-class system. Produces `specs/tech-architecture/eNN-TEST_PLAN_LATEST.md`.
11 
12## Pre-flight
13- Read `specs/epics/eNN-*/` story list.
14 
15## Core Workflow
161. **Analyze Epic**: Read sliced stories in the active epic capsule.
172. **Risk Assessment**: Map behaviors to P0–P3 risk tiers.
183. **Level Strategy**: Classify each scenario (Unit, Integration, E2E).
194. **Fixture Design**: Plan factories, network intercepts, mocks (see REFERENCE.md).
205. **NFR Plan**: Define verifiable commands for Non-Functional Requirements. Skip if `--lite`.
216. **Publish**: Generate `specs/tech-architecture/eNN-TEST_PLAN_LATEST.md`.
22 
23## Hard Gates & Guardrails
24- **DO NOT** write test code or production code during this skill.
25- Scenario ID format MUST be: `SC-eNNsYY-P{0|1|2|3}-NN`.
26- `plan-work` MUST reference these scenario IDs in its §17 Gherkin acceptance criteria.
27- Default to pushing tests to the lowest possible level.
28 
29## Execution Modes
30- `$bmad plan-tests`: Standard execution.
31- `$bmad plan-tests --lite`: Skips NFRs and complex fixture planning.
32 
33## Verify
34 
35→ verify: `test -f specs/tech-architecture/e32-TEST_PLAN_LATEST.md`
36 
37## Handoff
38 
39Gate: READY -> next: plan-work
40Writes: state.yaml handoff.next_skill = plan-work
41 
42---
43 
44# Plan Tests — Reference
45 
46## Test Plan Template (`specs/tech-architecture/eNN-TEST_PLAN_LATEST.md`)
47 
48```markdown
49# Test Design: [eNN-slug]
50 
51## 1. Risk Matrix & Scenarios
52| Scenario ID | Behavior Description | Risk | Test Level | Target File/Module |
53|-------------|----------------------|------|------------|--------------------|  
54| SC-P0-01    | Primary checkout     | P0   | Integration | checkout.spec.ts  |
55 
56## 2. Fixture Architecture & Isolation
57- Data Factories: (e.g. UserFactory)
58- Network Intercepts: (e.g. MSW handlers)
59- Database State: (e.g. in-memory SQLite)
60 
61## 3. NFR Verification
62| NFR Type | Requirement | Verification Command |
63|----------|-------------|----------------------|
64| Perf     | < 200ms     | `npm run test:perf`  |
65 
66## 4. Out of Scope
67- [Explicitly excluded testing areas]
68```
69 
70## Fixture Planning Guidance
71 
72- **Data Factories**: Prefer factory functions over manual object construction.
73- **Network Intercepts**: For frontend integration tests, use tools like Mock Service Worker (MSW) to intercept and mock HTTP requests.
74- **Database State**: For backend tests, use a clean database state per test or an in-memory database to ensure isolation.
75