What problem does it solve? Tests often verify mock behavior instead of real behavior, pollute production classes with test-only methods, or mock dependencies without understanding their side effects, producing suites that pass for the wrong reasons and fail mysteriously. ## Core Features & Use Cases - Mock Behavior Detection: Identifies assertions that verify mock existence rather than real component behavior, with gate functions to run before asserting on mock elements. - Production Code Protection: Prevents test-only methods like cleanup destroy() calls from leaking into production classes by moving them to test utilities. - Dependency-Aware Mocking: Enforces understanding of side effects before mocking, complete mock structures mirroring real API responses, and minimal mocking at the correct level. - Use Case: While writing a test that mocks a service layer, the gate functions prompt you to check whether the test depends on the mocked method's side effects, so you mock the slow external call instead of the high-level method the test relies on. ## Quick Start Review my test file for mock-related anti-patterns and suggest fixes before I commit it.
