testing-anti-patterns

Test anti-patterns happen when tests assert on mock behavior rather than verifying real code execution. You can identify them by auditing failing tests for mock-behavior assertions, test-only methods, and unclear dependencies, then refactoring to enforce clear separation between test utilities and production classes.

Preventing test-only methods in production code requires enforcing clear separation between test utilities and production classes. Discourage adding test-only methods and unclear dependencies by applying anti-pattern checks during code reviews to guide refactors and maintain code quality.

TDD helps avoid mocking anti-patterns by ensuring tests exercise real code behavior rather than asserting on mocks. Enforcing TDD practices prevents mocks from polluting production code, improves test reliability, and guides refactors when unclear dependencies are discovered.

To refactor a failing test for TDD alignment, audit the test to identify anti-patterns like mock-behavior assertions or test-only methods. Remove unclear dependencies and refactor the example to ensure tests exercise real code with complete mocks and clear separation from production classes.

You should not use mocking when it leads to asserting on mock behavior rather than verifying real code execution. Avoid mocking that pollutes production code with test-only methods or unclear dependencies, and refactor to enforce TDD practices with clear separation between test utilities and production classes.