domains / families / software-engineering / exp-mock-usage-analysis

exp-mock-usage-analysis

separate

Audits .NET test mock usage by tracing each mock setup through the production code's execution path to find dead, unreachable, redundant, or replaceable mocks. Use when the user asks to audit mock usage, find unused or unnecessary mock setups, check if mocks are needed, reduce mock duplication or over-mocking, simplify test setup, or review whether mock configurations like ILogger/IOptions should use real implementations instead. Supports Moq, NSubstitute, and FakeItEasy.

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)

Skill page

Source