When should I use integration tests instead of mocks?

If your mock setup becomes longer than the test logic itself or if you are mocking everything in sight, it is a red flag that an integration test would be simpler and more effective.

Why shouldn't I add test-only methods to production code?

Adding test-only methods pollutes the production API, increases the surface area for bugs, and creates confusion for other developers about which methods are safe to use in a live environment.

How does this skill improve AI-generated tests?

It forces Claude to focus on verifying real behavior and prevents it from taking shortcuts like creating partial mocks that might hide downstream bugs.

What are testing anti-patterns?

Testing anti-patterns are common but suboptimal testing habits, such as asserting on how a mock is called rather than the outcome of the code, or polluting production classes with methods used only in tests.

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

Yes, it is designed to be complementary to TDD. While strict TDD prevents many anti-patterns naturally, this skill provides a safety net during refactoring and modification of existing tests.

Testing Anti-Pattern Guard

Name: Testing Anti-Pattern Guard
Author: LerianStudio

byLerianStudio

•

セキュリティとテスト

Enforces high-quality testing standards by preventing mock-testing, production code pollution, and brittle dependency isolation.

概要

The Testing Anti-Pattern Guard is a specialized workflow skill designed to maintain the integrity of your test suite and production codebase. It acts as a quality gate that prevents common software engineering pitfalls such as asserting on mock behavior instead of real logic, adding test-only methods to production classes, and creating incomplete mocks that fail silently. By enforcing a 'test real behavior' philosophy and promoting TDD principles, this skill ensures that your automated tests remain reliable, maintainable, and truly reflective of your application's health.

主な機能

Prevents assertions on mock elements to ensure real behavior is tested
Detects overly complex mock setups that should be integration tests
Provides real-time gates during test modification and refactoring
Identifies and blocks test-only methods from leaking into production code
Enforces complete data structure mirroring for robust API mocking
17 GitHub stars

ユースケース

Ensuring AI-generated tests meet professional engineering standards
Maintaining a clean production API by moving test utilities to dedicated helpers
Refactoring brittle test suites that pass for the wrong reasons

概要

主な機能

Prevents assertions on mock elements to ensure real behavior is tested
Detects overly complex mock setups that should be integration tests
Provides real-time gates during test modification and refactoring
Identifies and blocks test-only methods from leaking into production code
Enforces complete data structure mirroring for robust API mocking
17 GitHub stars

ユースケース

Ensuring AI-generated tests meet professional engineering standards
Maintaining a clean production API by moving test utilities to dedicated helpers
Refactoring brittle test suites that pass for the wrong reasons