testing-anti-patterns

Mock behavior assertions test the mock's existence rather than verifying actual component functionality. This anti-pattern gives false confidence in test coverage. The testing-anti-patterns skill identifies these cases in JavaScript and TypeScript test suites, guiding refactors toward real behavior verification for reliable tests.

Test-only methods pollute production classes and violate separation of concerns, creating maintenance debt and hiding design issues. The skill prevents this anti-pattern by enforcing production code purity, ensuring tests interact with actual public APIs rather than backdoor methods.

Over-mocking breaks test logic by replacing too many dependencies before understanding their actual behavior. Strategic mocking requires understanding dependencies first. This skill guides correct mocking levels with complete data structures, preventing tests that pass but don't validate real interactions.

Yes. Incomplete mocks with partial data structures or misaligned expectations cause tests to pass spuriously. The skill detects these governance violations across JavaScript and TypeScript tests, guiding mocks toward completeness and alignment with actual component behavior.

False-confidence tests often assert on mocks, use incomplete stubs, or test implementation details instead of behavior. This skill detects these patterns in unit test suites and enforces governance rules that redirect tests toward real behavior verification, improving reliability.

The skill analyzes unit tests in JavaScript and TypeScript test suites to identify anti-patterns regardless of framework. It focuses on governance rules that apply across mock libraries, guiding refactors toward real behavior verification and production code purity.