marsai:testing-anti-patterns

Identify testing anti-patterns by analyzing unit tests for test-only methods, incomplete mocks, and mock-centric assertions that mask real behavior. This enforces real behavior testing over mock-centric assertions to reduce maintenance burden and prevent false confidence.

Mocking too much creates false confidence because it masks real behavior behind incomplete mocks, causing tests to pass without verifying actual dependencies. Enforcing mock discipline ensures rigorous understanding of dependencies before introducing mocks to validate real behavior.

Enforce strict TDD guidance and mock discipline by applying principles that flag test-only methods and incomplete mocks, driving design through TDD. This remediates testing anti-patterns by guiding refactors toward production-safe utilities and well-structured test suites.

Fix incomplete mocks and test-only methods by applying anti-pattern remediation steps that guide refactors toward production-safe utilities. This process eliminates incorrect testing practices, aligning tests with real behavior instead of relying on mock-centric assertions.

Yes, you can review a failing test suite and apply anti-pattern fixes to align tests with real behavior. It applies to codebases with unit tests, test utilities, and mocks, providing actionable gates to enforce correct testing practices.