Why should I avoid test-only methods in production classes?

Test-only methods pollute your production API and can create security risks or maintenance debt if those methods are accidentally invoked in a live environment.

Does this skill support Test-Driven Development (TDD)?

Yes, it actively encourages a TDD cycle by flagging implementations that lack accompanying tests or treat integration testing as an afterthought.

When should I use this skill?

Use this skill whenever you are writing or modifying tests, adding mocks to a project, or considering adding hooks to production code for testing purposes.

How does this skill handle mock objects?

It enforces that mocks are used only for isolation, must mirror real schemas entirely, and should never be the subject of a test assertion.

What is the main goal of the testing anti-patterns skill?

The primary goal is to ensure that tests validate real application behavior rather than the behavior of mocks, while keeping production code clean of test-specific helpers.

Testing Anti-Pattern Guardrails

Name: Testing Anti-Pattern Guardrails
Author: tjboudreaux

bytjboudreaux

0•

セキュリティとテスト

Enforces high-quality testing practices by identifying and preventing common anti-patterns like testing mocks or polluting production code.

This skill provides a set of strict engineering guardrails for Claude Code to ensure unit and integration tests remain robust and maintainable. It prevents common but costly mistakes, such as asserting on mock behavior instead of real functionality, adding test-specific methods to production classes, and creating incomplete mocks that fail to reflect real API schemas. By applying 'Iron Laws' of testing during the development cycle, this skill promotes a Test-Driven Development (TDD) mindset, ensuring that mocks are used strictly for isolation rather than as the primary subject of validation.

主な機能

01Validates mock completeness against real API and data schemas

02Promotes a TDD-first approach to ensure integration tests are prioritized

03Prevents the addition of test-only helper methods to production source code

040 GitHub stars

05Enforces dependency understanding before allowing complex mock implementations

06Detects assertions on mock objects instead of real component behavior

ユースケース

01Maintaining clean production APIs by moving test utilities to dedicated helpers

02Enforcing high engineering standards during feature implementation and code reviews

03Refactoring legacy test suites to remove fragile or 'shallow' mocks

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tjboudreaux/cc-engineering-skills eng-testing-anti-patterns

For use in Claude.ai and ChatGPT

Download Skill