@rune-kit/rune 2.2.4 → 2.2.6

package/skills/test/SKILL.md

@@ -3,7 +3,7 @@ name: test
 description: "TDD test writer. Writes failing tests FIRST (red), then verifies they pass after implementation (green). Covers unit, integration, and e2e tests."
 metadata:
   author: runedev
-  version: "0.5.0"
+  version: "0.7.0"
   layer: L2
   model: sonnet
   group: development
@@ -208,14 +208,14 @@ For non-trivial features (3+ test files or 20+ test cases), create a `TEST.md` i
 - `test_e2e.py`: ~XX E2E tests planned (L3/L4)
 
 ## Unit Test Plan (L1)
-| Module | Functions | Edge Cases | Est. Tests |
-|--------|-----------|------------|------------|
-| `core/auth.py` | login, register, refresh | expired token, invalid creds, rate limit | 12 |
+| Module | Functions | Edge Cases | Est. Tests | Req IDs |
+|--------|-----------|------------|------------|---------|
+| `core/auth.py` | login, register, refresh | expired token, invalid creds, rate limit | 12 | REQ-001, REQ-003 |
 
 ## E2E Scenarios (L3/L4)
-| Workflow | Simulates | Operations | Verified |
-|----------|-----------|------------|----------|
-| User signup | New user onboarding | register → verify → login | Token valid, profile created |
+| Workflow | Simulates | Operations | Verified | Req IDs |
+|----------|-----------|------------|----------|---------|
+| User signup | New user onboarding | register → verify → login | Token valid, profile created | REQ-005 |
 
 ## Realistic Workflow Scenarios
 - **[Name]**: [Step 1] → [Step 2] → verify [output properties]
@@ -230,6 +230,12 @@ For non-trivial features (3+ test files or 20+ test cases), create a `TEST.md` i
 - Total: XX | Passed: XX | Failed: 0
 - Execution time: X.Xs | Coverage: XX%
 
+## Requirement Coverage
+| Req ID | Test File(s) | Status |
+|--------|-------------|--------|
+| REQ-001 | `test_auth.py::test_login` | ✅ Covered |
+| REQ-002 | — | ❌ Not covered |
+
 ## Gaps
 - [Areas not covered and why]
 ```
@@ -261,6 +267,25 @@ For non-trivial features (3+ test files or 20+ test cases), create a `TEST.md` i
 - `browser-pilot` (L3): Phase 4 — e2e and visual testing for UI flows
 - `debug` (L2): Phase 5 — when existing test regresses unexpectedly
 
+## Data Flow
+
+### Feeds Into →
+
+- `cook` (L1): test results (pass/fail/coverage) → cook's Phase 5 quality gate evidence
+- `completion-gate` (L3): test runner stdout → evidence for "tests pass" claims
+- `fix` (L2): failing test output → fix's target (what to make green)
+
+### Fed By ←
+
+- `plan` (L2): phase file test tasks → test's RED phase targets (what to test)
+- `review` (L2): untested edge cases found during review → new test targets
+- `fix` (L2): implemented code → test's GREEN phase verification target
+
+### Feedback Loops ↻
+
+- `test` ↔ `fix`: test writes failing tests (RED) → fix implements to pass → test verifies (GREEN) → if new failures emerge, loop continues
+- `test` ↔ `debug`: test discovers regression → debug diagnoses root cause → test writes regression test to prevent recurrence
+
 ## Anti-Rationalization Table
 
 | Excuse | Reality |
@@ -375,6 +400,18 @@ Known failure modes for this skill. Check these before declaring done.
 | Modifying source files to make tests work | HIGH | Role boundary: test writes test files ONLY — source changes go to rune:fix |
 | Test-only methods leaking into production code | MEDIUM | Anti-Pattern 2 gate: if method only called by tests → move to test utilities |
 
+## Self-Validation
+
+```
+SELF-VALIDATION (run before emitting Test Report):
+- [ ] Every test file has at least one assertion — no empty test bodies
+- [ ] RED phase output shows actual failures (not "0 tests") — tests were real, not stubs
+- [ ] No test modifies source code — test files only, source changes belong to fix
+- [ ] Test names describe behavior, not implementation ("should reject expired token" not "test function X")
+- [ ] No mocks of the thing being tested — only mock external dependencies
+- [ ] If BA requirements exist (REQ-xxx), every requirement has at least one test — check plan's Traceability Matrix
+```
+
 ## Done When
 
 - Test framework detected from project config files
@@ -383,6 +420,7 @@ Known failure modes for this skill. Check these before declaring done.
 - After implementation: all tests PASS (GREEN phase — actual pass output shown)
 - Coverage ≥80% verified via verification
 - Test Report emitted with framework, test count, RED/GREEN status, and coverage
+- Self-Validation: all checks passed
 
 ## Cost Profile