How does this skill prevent production code pollution?

It identifies methods intended only for testing and provides guidance on moving them to external test-utility files, keeping production classes focused on business logic.

What are the Iron Laws of testing mentioned in this skill?

The Iron Laws are: NEVER test mock behavior, NEVER add test-only methods to production classes, and NEVER mock without fully understanding the underlying dependencies.

Why is 'testing mock behavior' considered an anti-pattern?

Testing mock behavior only verifies that your mock works, not that your application works. This leads to tests that pass even when the real component is broken.

How does this skill handle incomplete mocks?

It enforces a rule to mirror the complete real-world data structure. Partial mocks are flagged because they hide structural assumptions and lead to silent failures in downstream code.

Testing Anti-Patterns Guard

Name: Testing Anti-Patterns Guard
Author: cipherstash

bycipherstash

•

安全与测试

Enforces robust software testing standards by identifying and preventing brittle mocks, production code pollution, and incomplete test data structures.

关于

The Testing Anti-Patterns skill acts as a guardrail for your quality assurance process, ensuring that tests verify real application behavior rather than the behavior of mocks. It implements the 'Iron Laws' of testing to prevent the common pitfalls of TDD, such as adding test-only methods to production classes or mocking dependencies without a full understanding of their side effects. By utilizing specialized 'Gate Functions,' this skill helps developers maintain a clean separation between production logic and test utilities while ensuring that every mock mirrors reality with structural completeness.

主要功能

Identifies and blocks the addition of test-only methods to production classes
Prevents assertions on mock existence to focus on real component behavior
Provides Gate Functions to validate testing strategies before implementation
4 GitHub stars
Enforces structural completeness for mocks to prevent silent downstream failures
Promotes strict TDD cycles to ensure tests are meaningful and reliable

使用场景

Onboarding developers to high-standard TDD environments with automated best-practice guidance
Sanitizing production codebases by migrating test-specific logic to external utility helpers
Refactoring brittle test suites that fail due to implementation details rather than logic errors

关于

主要功能

Identifies and blocks the addition of test-only methods to production classes
Prevents assertions on mock existence to focus on real component behavior
Provides Gate Functions to validate testing strategies before implementation
4 GitHub stars
Enforces structural completeness for mocks to prevent silent downstream failures
Promotes strict TDD cycles to ensure tests are meaningful and reliable

使用场景

Onboarding developers to high-standard TDD environments with automated best-practice guidance
Sanitizing production codebases by migrating test-specific logic to external utility helpers
Refactoring brittle test suites that fail due to implementation details rather than logic errors