Audit .NET test value

Identify what each test can detect before recommending a change. Optimize confidence and maintenance cost, not test count or deleted lines.

For a review, produce findings without editing tests or production code. For authorized cleanup, establish evidence before changing each candidate.

Establish the audit boundary

Read repository instructions, the requested scope, test projects, and CI selection. Preserve the existing language, SDK, dependencies, framework, and runner.

Identify the selected target frameworks and execution mechanism: VSTest, Microsoft.Testing.Platform, Expecto executable, or repository script. Do not assume their filter syntax is interchangeable.

For subsystem or repository-wide work, use the suite inventory procedure. A sample can inform priorities but cannot complete a broader audit.

For each proposed addition or existing candidate, establish: