detect-static-dependencies

To find hard-to-test static dependencies in C# code, scan your files or solution for unmockable APIs like DateTime, File, Directory, and HttpClient. This produces a ranked report of call-site frequencies and affected files to prioritize testability improvements.

Common static coupling issues blocking C# unit testing include direct calls to DateTime, File/Directory, Environment, HttpClient, Console, and Process. These unmockable static APIs prevent isolated testing and require specific abstraction replacements to resolve.

You can scan a .csproj or .sln for unmockable static API calls by applying category filtering and exclusion handling for obj and bin directories. This aggregates each dependency category to map recommended .NET abstraction replacements.

Recommended .NET abstractions to replace static dependencies include TimeProvider for time, System.IO.Abstractions for filesystem access, and IHttpClientFactory for network calls. These replacements enable effective mocking and improve code testability.

Yes, you can and should exclude generated code directories when scanning C# files for testability blockers. The scanning process explicitly handles exclusion for obj and bin folders to ensure the ranked report reflects only your source code.

The best way to plan a migration strategy for untestable static C# code is to use a ranked static dependency report showing top patterns and most affected files. This targeted approach maps each category to its recommended .NET abstraction replacements for prioritized refactoring.