specflow-testslisted

# Specflow Testing ## Core Principle **A test that does not execute is not a test.** A test file that exists but throws on import, crashes on setup, or stubs its assertions with `expect(true).toBe(true)` is documentation, not a test. Testing is not complete until every test runs, passes or fails for legitimate reasons, and the verification agent confirms quality. ## Agent Architecture This skill delegates to three types of agents. Each has a distinct scope and context. | Agent | Context contains | Does NOT contain | Spawned by | |---|---|---|---| | Infrastructure agent | Project stack, package files, configs | Specs, test files | Orchestrator | | Generation agent (per domain) | That domain's specs + fixtures + conventions | Other domains, test results | Orchestrator | | Verification agent | Test files + spec tree | Generation context, fixture internals | Orchestrator | | Blind reader (per domain per layer) | Test files only | Specs, fixtures, generation context | Verification agent | **The verification agent is separate from the generation agents.** It reads the tests with fresh eyes — it wasn't involved in writing them. The blind reader sub-agents it spawns have even less context — they see only the test code, nothing else. ## Cortex Awareness When the project has a `.cortex/` directory, read the knowledge layer before generating (skip this section cleanly when `.cortex/` is absent): 1. **Compass rules become test assertions (design §8.4 bridge 1).** Before generati