specflow-testslisted

# Specflow Testing ## When to use Complete testing framework for Specflow projects. Builds the test infrastructure first, then generates tests across four layers (Atomic, Spec, Journey, Scenario) via delegated agents per domain, then hands off to a separate verification agent that runs all tests, performs adversarial quality checks, and loops until everything passes. A test that does not execute is not a test. Use this skill for: generating tests from specs, setting up test infrastructure, creating test fixtures, designing scenario tests, running test suites, or auditing coverage. ## The Iron Law NO TEST ENTERS THE SUITE UNTIL IT HAS BEEN WATCHED FAILING FOR THE RIGHT REASON Violating the letter of this law is violating the spirit. If you find yourself constructing a reading under which this test does not need watching, that construction is the violation. Hardening mechanisms per `skills/_conventions/hardening.md`. ## 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. **A test that has only ever been seen passing is not yet evidence.** Green tells you nothing on its own: the test may be right, may assert nothing, or may be exercising a different path than the one it names. All th