mock-detection

To detect inappropriate mock usage in unit tests, analyze test files to identify violations of testing best practices. This Skill evaluates mock appropriateness based on test type, pinpointing anti-patterns like mocking the system under test to ensure your tests reflect real-world behavior.

Common mock anti-patterns causing false test confidence include T1-T4 violations, such as mocking the system under test or verifying mock calls without asserting results. Identifying these specific anti-patterns helps refactor tests to accurately reflect real-world behavior.

To analyze an integration test file for mocking best practices, pass the file to a mock analysis process. It evaluates if mocks are used correctly based on the test type, identifying violations and prioritizing findings by severity to maintain test confidence.

Yes, mock appropriateness analysis works for end-to-end tests. It evaluates mock usage correctness across unit, integration, and E2E test types, identifying specific anti-patterns and prioritizing findings based on severity and impact on overall test confidence.

You should audit your test suite for excessive mock usage when tests provide a false sense of security. A test audit identifies T1-T4 violations and prioritizes findings by severity, helping you refactor mocks for true effectiveness and reliable confidence.

The best way to refactor tests that mock the system under test is to run a deep mock analysis to identify T1-T4 violations. This analysis tracks violation scope and prioritizes findings by impact, guiding targeted refactoring for true test effectiveness.