testing-anti-patterns

Testing anti-patterns occur when tests pass because mocks behave as expected, not because production code works correctly. Look for tests that only verify mock interactions without exercising actual component logic, dependencies, or lifecycle—these miss real bugs and fail to validate genuine behavior.

Test-only methods pollute production code and signal weak test design. Instead, refactor to test through public APIs, use dependency injection for real dependencies, and write integration tests that exercise actual behavior paths. This keeps production code clean and tests honest.

Mocks decouple tests from real behavior, allowing tests to pass while production code fails. Over-mocking hides integration issues, API contract violations, and lifecycle problems. Anti-pattern detection prevents tests from becoming false positives that don't catch bugs in actual usage.

Replace mocks with real implementations where feasible, use test doubles sparingly for external dependencies only, and verify behavior end-to-end. Enforce production code quality gates that reject test-only changes and incomplete mocks, ensuring tests reflect how code actually runs.

Yes. Anti-pattern detection spans all test levels to curb mocking of production code, prevent test-only methods, and eliminate misleading mocks. Apply enforcement across your test suite to ensure consistency and catch behavioral gaps that unit-test-only mocking would miss.

This signals mocking anti-patterns: tests verify mock behavior instead of real behavior. Identify over-mocked dependencies, test-only production methods, and incomplete mocks. Restructure tests to exercise actual code paths, use real objects where safe, and gate functions that prevent mock-only validation.