testing-anti-patterns

To prevent mocking behavior, apply automated gate checks that block tests from asserting mocks exist or were called. This enforces verifying real behavior and ensures mocks mirror actual dependencies. Mocks should validate slow or external parts only, reflecting complete real data structures and documented fields.

Stop test-only production code by enforcing production code integrity checks. This prohibits test-only lifecycle or cleanup methods from entering production code, preventing flawed tests from misleading software quality and maintaining clear separation between test utilities and production logic.

Common testing anti-patterns include asserting mock behavior instead of real outcomes, incomplete mocks lacking documented fields, and adding test-only methods to production code. These flawed testing practices undermine software quality by creating fragile tests that do not validate actual dependencies.

Align mocking practices with test-driven development by validating dependencies before mocking them. Ensure mocks mirror complete real data structures, targeting only slow or external parts, which keeps testing a first-class activity and prevents flawed tests from undermining your test-driven development workflow.

You should not use mocks when verifying real behavior or validating internal dependencies. Mocks should target only slow or external parts of the system, ensuring mocks reflect complete real data structures and documented fields rather than mocking behavior that should be tested directly.

Yes, this skill supports code review workflows by applying gate checks during test creation and when modifying mocks or adding test utilities. It enforces production code integrity and prevents flawed tests, ensuring quality assurance standards are met during reviews.