What problem does it solve? .NET test suites often accumulate mock setups that are never exercised, unreachable due to guard clauses, duplicated across tests, or mocking types that should use real implementations, making tests harder to maintain and slower to understand. ## Core Features & Use Cases - Execution Path Tracing: Traces each mock setup through the production method's control flow to classify it as used, unreachable, unused, or redundant. - Replaceable Mock Detection: Flags mocks of stable framework types like ILogger and IOptions that should use NullLogger or Options.Create instead, while confirming external boundaries stay mocked. - Multi-Framework Support: Recognizes Moq, NSubstitute, and FakeItEasy patterns and uses the correct framework terminology in findings. - Use Case: A team inherits a large test suite with heavy over-mocking; run this audit to get a per-test report of which setups to delete, which to consolidate into shared fixtures, and which to replace with real implementations. ## Quick Start Audit the mock usage in my OrderService tests by tracing each setup through the production code and telling me which mocks are unnecessary.
