Why shouldn't I use incomplete mocks?

Partial or incomplete mocks hide structural assumptions. If downstream code depends on a field you didn't mock, the test might pass while the real integration fails.

Does this skill work with Test-Driven Development (TDD)?

Yes, it is designed to complement TDD by ensuring that tests are written first and that they fail against real implementations before any mocking is introduced.

What are testing anti-patterns?

Testing anti-patterns are common but counterproductive habits in software testing, such as asserting that a mock exists instead of verifying the actual behavior of the code under test.

How does this skill prevent production code pollution?

It enforces the 'Iron Law' that no method should be added to a production class if its only purpose is to support a test; instead, it guides developers to use external test utilities.

Testing Anti-Patterns Guard

Name: Testing Anti-Patterns Guard
Author: AlabamaMike

byAlabamaMike

Seguridad y Pruebas

Prevents common software testing errors by enforcing best practices for mocking, production code isolation, and test-driven development.

Acerca de

The Testing Anti-Patterns Guard is a specialized Claude Code skill designed to improve test reliability and maintainability. It acts as a set of guardrails during the development process, preventing developers from falling into traps like testing mock existence instead of behavior, polluting production classes with test-only methods, and creating incomplete mocks that lead to false positives. By applying strict 'Iron Laws' and 'Gate Functions,' this skill ensures that your test suite remains a robust reflection of your system's real-world behavior while encouraging a disciplined Test-Driven Development (TDD) workflow.

Características Principales

0 GitHub stars
Provides logic-based Gate Functions to evaluate dependency understanding before mocking
Blocks the addition of test-only methods to production classes to maintain code purity
Identifies and prevents the testing of mock existence over real system behavior
Enforces structural completeness for API and data mocks to prevent silent failures
Promotes strict TDD cycles to ensure comprehensive test coverage during implementation

Casos de Uso

Onboarding developers to high-quality TDD and mocking standards
Enforcing clean architecture by moving test helpers to dedicated utility files
Auditing existing test suites for brittle mocks and production code pollution

Acerca de

Características Principales

0 GitHub stars
Provides logic-based Gate Functions to evaluate dependency understanding before mocking
Blocks the addition of test-only methods to production classes to maintain code purity
Identifies and prevents the testing of mock existence over real system behavior
Enforces structural completeness for API and data mocks to prevent silent failures
Promotes strict TDD cycles to ensure comprehensive test coverage during implementation

Casos de Uso

Onboarding developers to high-quality TDD and mocking standards
Enforcing clean architecture by moving test helpers to dedicated utility files
Auditing existing test suites for brittle mocks and production code pollution