test-antipatterns

Unit tests become brittle when assertions target mock interactions instead of real behavior. This Skill detects mock-driven assertions and unsafe mocking patterns, ensuring tests validate actual component behavior and remain stable during refactoring.

You can identify unsafe mocking patterns in TypeScript test files by reviewing assertions against mock elements and incomplete mock objects. This Skill analyzes test code to detect mock-centric validations and suggests safer test patterns with minimal necessary isolation.

Mock-driven assertion in integration tests occurs when tests verify that a mock was called rather than validating real system behavior. This Skill identifies these patterns and enforces real behavior validation with minimal mocking to prevent misleading integration test results.

To prevent test-only methods in production code, move test helpers and lifecycle methods into test utilities. This Skill detects accidental test-only APIs in production classes and enforces test utility separation to keep production code clean.

Yes, you can use this for code review of JavaScript and TypeScript testing. This Skill reviews test files and implementations to identify mock misuse, incomplete mock structures, and accidental test-only APIs, suggesting safer patterns and cleanup.

You should avoid mocks in unit tests when the dependencies do not compromise test reliability. This Skill helps determine the right level to mock by enforcing minimal necessary isolation and ensuring tests keep the side effects they depend on.