Testing Anti Patterns

Common mocking anti-patterns include writing tests that merely assert a mock's existence or verifying call counts instead of verifying real behavior. This skill guides teams in detecting these patterns and refactoring tests to use concrete dependencies and complete fixtures.

To refactor tests for real behavior verification, replace mock existence assertions with concrete dependencies and realistic test data. This skill helps you review existing test files, identify mock-heavy patterns, and implement test utilities to encapsulate repetitive setup without polluting production code.

TDD prevents testing anti-patterns by enforcing the red-green-refactor cycle, ensuring tests drive real behavior verification. This skill promotes TDD-driven improvements by discouraging test-only production code and guiding robust test design across languages and frameworks.

Incomplete mock structures cause silent test failures because they lack realistic data needed to trigger actual execution paths. This skill emphasizes test-data completeness by guiding you to use complete mock structures and realistic fixtures that prevent silent failures across unit and integration tests.

Yes, testing anti-pattern detection applies across languages and test frameworks. This skill provides framework-agnostic guidance for reviewing mock usage, fixture design, and test data management in both unit and integration tests.

You should avoid mocks when they only assert call counts or mock existence rather than verifying real behavior. This skill guides you to replace such mock-heavy patterns with concrete dependencies and complete fixtures to ensure robust test design and prevent silent failures.