bee:testing-anti-patterns

Unit tests that pass but miss real bugs often occur because the test verifies mock behavior instead of actual code behavior. This testing anti-pattern creates a false sense of security by validating mock configurations rather than the real system's output.

To prevent test-only methods from polluting production code, enforce production purity by reviewing code interactions. This ensures test-specific methods are not introduced into production logic, maintaining clean boundaries between test infrastructure and application code.

Common mocking anti-patterns in TDD include mocking dependencies without understanding their side effects and testing mock behavior instead of real outputs. These practices lead to brittle tests that fail to accurately reflect real system behavior.

Review existing test code for common testing anti-patterns by analyzing test logic and production code interactions. Identify mock abuse, verify actual behavior is tested, and check for test-specific methods improperly introduced into production code.

Avoid mocking dependencies in unit testing when you lack a thorough understanding of their side effects. Mocking without analyzing dependency behavior leads to misleading tests that do not accurately verify robust and reliable software interactions.