check-coverage

To check unit test coverage, you can run dotnet test with coverlet.msbuild using OpenCover output, analyze the coverage.opencover.xml report, and classify classes against an 85% threshold to identify untested or critically under-tested code. It highlights classes below 60% as critical and 60–84% as needing attention.

You can find untested classes by restricting test execution to a specific layer or test project. After running dotnet test with coverlet.msbuild, the coverage analysis parses the OpenCover XML output to compute line coverage metrics per class and reports which classes lack tests within that targeted scope.

The 85% test coverage quality gate is a fixed threshold used to classify code risk in .NET repositories. Classes with coverage at or above 85% conform, those between 60–84% require attention, and classes below 60% or with no tests are flagged as critical risks.

No, this coverage analysis tool never modifies code or auto-triggers test creation. It strictly computes line coverage per class from the coverlet-generated OpenCover XML report, classifies the results by threshold tiers, and reports the findings in chat to guide manual improvements.

Yes, you can verify your entire .NET test suite coverage by executing all tests with dotnet test and coverlet.msbuild. The tool reads the generated coverage.opencover.xml file, analyzes line coverage across the full suite, and reports any classes failing the 85% quality threshold.

You need an OpenCover XML report because it provides the structured line coverage data required to compute metrics per class. The tool parses this specific coverlet-generated output format to accurately locate classes with low or missing test coverage and evaluate them against the 85% threshold.