What problem does it solve? Teams often write tests that chase coverage percentages instead of catching real bugs, leaving critical paths like payments, auth, and data-destroying operations untested while flaky suites erode trust. ## Core Features & Use Cases - Test Pyramid Guidance: Assigns each behavior to the right layer (unit, integration, e2e) with rules for pushing tests as low as possible while still testing real behavior. - Prioritized Test Planning: Ranks what to test first — money and auth paths, data-destroying operations, boundary logic, error paths, and regression locks for fixed bugs. - Flaky Test Diagnosis: Provides an ordered diagnostic flow for shared state, time dependencies, async races, network calls, and test-order dependencies. - Suite Review: Audits existing suites by checking whether recent production bugs would have been caught, flagging assert-free tests and mock-only assertions. - Use Case: When asked "how should we test this checkout feature", produce a structured test plan with critical behaviors, edge cases, error paths, explicit out-of-scope items, and an estimated unit/integration/e2e split. ## Quick Start Ask the agent to design a test plan for your feature, for example: create a test strategy for the coupon discount endpoint including edge cases and error paths.
