comprehensive-test-strategylisted

# Comprehensive Test Strategy ## Why this exists BDD scenarios prove a feature *behaves* correctly, but that's roughly a third of what elite teams test. They also verify the units in isolation, that services don't break each other's contracts, that the system holds up under load, that it degrades gracefully when infrastructure fails, and that the test suite itself is trustworthy (fast, deterministic, meaningfully covering the code). This skill owns that broader strategy so "we have tests" means "we have the *right* tests at the right levels," not just a pile of end-to-end checks. This skill is the companion to `bdd-comprehensive-testing`. That skill owns the Gherkin/behavioral layer and wires the suite into CI; this skill decides the *full mix* of test types and adds the ones BDD doesn't cover. Use them together — don't duplicate the behavioral scenarios here. ## The core principle **Test at the lowest level that can catch the bug, and match the test type to the risk.** Fast, isolated tests for logic; a smaller number of integration tests for the seams; fewer, high-value end-to-end/BDD tests for critical journeys; plus specialized tests (contract, load, chaos) for the risks that unit tests can't see. A suite that's all end-to-end is slow, flaky, and expensive; a suite that's all unit misses integration and scale failures. ## The workflow ### Step 1: Design the test mix for the change (the pyramid) Read `references/test-pyramid-and-types.md`. Decide the right proportio