testing-anti-patterns

To stop tests validating mock behavior, apply anti-pattern gates that prohibit asserting on mock elements and require understanding real side effects before mocking. This ensures your test suite validates actual application logic rather than fragile mock interactions.

Common testing anti-patterns include asserting on mock existence, adding test-only methods to production code, mocking without understanding dependencies, and providing incomplete mock data that fails to mirror real response schemas.

Decide between unit isolation and integration realism by using decision gate checks before mocking. Evaluate whether to unmock, mock at a lower level, or use real dependencies across UI and service layers to maintain valid side effects.

Never add test-only utility methods to production classes. Contaminating production code with test-only methods is an anti-pattern that breaks dependency-driven side effects and compromises actual behavior validation.

Review a test change by identifying which anti-patterns it might introduce, then rewrite the test to validate real behavior. Ensure mocks mirror complete response schemas and avoid asserting on mock elements directly.