What problem does it solve? Teams adopt test pyramids, trophies, or honeycombs by fashion rather than evidence, ending up with suites that miss real defects, duplicate assertions across levels, and grow too slow to run. This Skill provides a framework for choosing test levels, budgets, and contract testing based on where defects actually occur. ## Core Features & Use Cases - Shape Selection by Evidence: Classify recent production defects to decide between pyramid, trophy, or honeycomb distributions instead of copying a diagram. - Level Assignment Rules: Test each behaviour at the narrowest level where it is fully expressed, with explicit guidance on what not to unit test (getters, framework calls, wiring). - Contract Testing: Consumer-driven contract tests with provider-side verification and can-i-deploy gates for microservice boundaries. - Runtime Budgets: Per-tier time budgets (unit, integration, contract, end-to-end) enforced in CI to prevent suite degradation. - Use Case: A team with a slow, flaky E2E-heavy suite uses the checklist to reclassify defects, push assertions down to unit and integration levels, and cap end-to-end tests at revenue-critical journeys. ## Quick Start Ask the assistant to review your current test suite distribution and recommend a testing strategy based on your recent production defects.
