How does this skill handle production code cleanliness?

It strictly prevents the addition of methods to production classes that are only used for testing purposes, suggesting the use of external test utilities instead.

Why should I avoid partial mocks according to this skill?

Partial mocks often hide structural assumptions and dependencies, leading to tests that pass even when the real integration would fail due to missing data fields.

What is the main goal of the Testing Anti-Patterns skill?

Its primary goal is to ensure tests verify real code behavior instead of just checking if mocks are functioning correctly, resulting in more reliable test suites.

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

Yes, it promotes the TDD cycle (Red-Green-Refactor) as the fundamental method to avoid common testing pitfalls and ensure code coverage is meaningful.

What are 'Gate Functions' in this context?

Gate Functions are specific decision-making checklists the skill uses to evaluate whether a mock, an assertion, or a new method is actually necessary before implementation.

Testing Anti-Pattern Prevention

Name: Testing Anti-Pattern Prevention
Author: seanGSISG

byseanGSISG

보안 및 테스팅

Enforces best practices in software testing by preventing mock reliance, production code pollution, and incomplete test doubles.

소개

This skill provides a rigorous framework for Claude to follow when writing or modifying tests, ensuring that verification focuses on real behavior rather than implementation details. It implements a set of 'Iron Laws' that prohibit testing mock existence, prevents the leakage of test-specific methods into production classes, and mandates a deep understanding of dependencies before applying mocks. By prioritizing Test-Driven Development (TDD) principles and providing specific 'Gate Functions' for decision-making, this skill helps developers build more resilient, maintainable, and meaningful test suites while avoiding the brittle tests that often plague complex software projects.

주요 기능

Enforces full schema completeness for mocked data structures to prevent silent failures
Provides 'Gate Functions' to validate testing logic and mock necessity
Blocks production code pollution by moving test-only methods to utilities
0 GitHub stars
Prevents testing of mock existence to ensure real behavior is verified
Promotes strict TDD cycles to ensure tests fail for the right reasons

사용 사례

Implementing new features using strict TDD workflows to ensure high code quality
Refactoring legacy test suites to remove brittle or over-complicated mocks
Auditing production classes to identify and remove test-only code leaks

소개

주요 기능

Enforces full schema completeness for mocked data structures to prevent silent failures
Provides 'Gate Functions' to validate testing logic and mock necessity
Blocks production code pollution by moving test-only methods to utilities
0 GitHub stars
Prevents testing of mock existence to ensure real behavior is verified
Promotes strict TDD cycles to ensure tests fail for the right reasons

사용 사례

Implementing new features using strict TDD workflows to ensure high code quality
Refactoring legacy test suites to remove brittle or over-complicated mocks
Auditing production classes to identify and remove test-only code leaks