domains / families / software-engineering / generate-testability-wrappers

generate-testability-wrappers

separate

DO NOT USE when the target already consumes an injected interface or built-in abstraction such as IFileSystem or TimeProvider, even if the request says "generate a wrapper"; no new wrapper is needed. Use only when C# source calls an ambient/static dependency and no injectable seam exists: first-time TimeProvider, IHttpClientFactory, or System.IO.Abstractions adoption; minimal Environment/Console/Process wrappers; IProcessRunner; DI registration; or an ambient seam that preserves a static API. Exclude static detection (detect-static-dependencies), migration to an existing/registered abstraction (migrate-static-to-wrapper), one blocked behavior plus deterministic tests (testability-obstacle), and general interface design.

When to use

• After running `detect-static-dependencies` and identifying which statics to wrap
• When the user asks to make a class testable by replacing statics with injected abstractions
• When adopting `TimeProvider` (.NET 8+) or `System.IO.Abstractions`
• When creating a custom wrapper for `Environment.*`, `Console.*`, or `Process.*`
• When a released static API needs an ambient seam because signatures cannot change

When not to use

• The user wants to find statics first (use `detect-static-dependencies`)
• The user wants to bulk-replace call sites (use `migrate-static-to-wrapper`)
• The static is already behind an interface

Skill page

Source