Mock Usage Analysis

Trace each mock setup through the production code's execution path to determine which setups are actually exercised at runtime and which are dead, unreachable, redundant, or replaceable with real implementations.

When to Use

• User asks to audit, review, or analyze mock usage in .NET tests
• User wants to find unused, unnecessary, or redundant mock setups
• User wants to simplify test setup or reduce over-mocking
• User asks whether mocks of ILogger, IOptions, or similar types are needed

When Not to Use

• User wants to write new mocks or tests (general testing guidance)
• User wants to detect non-mock test anti-patterns (use test-anti-patterns)
• User wants to migrate between mock frameworks (out of scope)

Inputs