Why is testing mock behavior considered an anti-pattern?

Testing a mock only verifies that the mock works, not the code. This leads to tests that pass even when the real component is broken, providing a false sense of security.

Can this skill help with incomplete API mocks?

Yes, it includes specific checks to ensure that mocks mirror the complete data structure of the real API, preventing silent failures when downstream code accesses fields that were omitted in a partial mock.

How does it prevent production code pollution?

It identifies methods created solely for testing purposes and directs the user to move that logic into dedicated test utilities, keeping production classes clean and focused on their primary lifecycle.

What are the 'Iron Laws' enforced by this skill?

The skill enforces three core rules: never test mock behavior, never add test-only methods to production classes, and never mock without fully understanding the underlying dependencies.

Testing Anti-Pattern Guard

Name: Testing Anti-Pattern Guard
Author: martin-janci

bymartin-janci

•

安全与测试

Prevents common software testing mistakes by enforcing strict principles against mock misuse and production code pollution.

关于

Testing Anti-Pattern Guard empowers Claude to identify and avoid the most frequent pitfalls in software testing, such as asserting on mock behavior instead of real logic, polluting production classes with test-only methods, and creating incomplete mocks that lead to silent integration failures. By applying rigorous Test-Driven Development (TDD) principles and specific 'Gate Functions,' this skill ensures your test suite remains robust, maintainable, and focused on verifying actual application behavior rather than implementation details.

主要功能

Enforces structural completeness for mocks to prevent downstream integration errors
Provides gate functions to validate the necessity and scope of mocks
Identifies assertions that mistakenly test mock existence instead of component behavior
1 GitHub stars
Flags and prevents the addition of test-only methods to production classes
Promotes strict TDD workflows to catch architectural issues early in development

使用场景

Refactoring legacy test suites that rely on fragile or over-complicated mocks
Conducting automated code reviews to catch production code pollution before deployment
Guiding the development of new features using clean, TDD-aligned testing patterns

关于

主要功能

Enforces structural completeness for mocks to prevent downstream integration errors
Provides gate functions to validate the necessity and scope of mocks
Identifies assertions that mistakenly test mock existence instead of component behavior
1 GitHub stars
Flags and prevents the addition of test-only methods to production classes
Promotes strict TDD workflows to catch architectural issues early in development

使用场景

Refactoring legacy test suites that rely on fragile or over-complicated mocks
Conducting automated code reviews to catch production code pollution before deployment
Guiding the development of new features using clean, TDD-aligned testing patterns