The old coverage was based upon every test. This is not necessary with ms code coverage. The old coverage would wait until tests have finished before starting the coverage tool to re-run all tests. With the old coverage FCC needed to copy your test dll and dependencies and run OpenCover or Coverlet on those files. If you experience issues then providing the logs from the output window will help to understand the nature of the problem. When the coverage becomes outdated, you can click the 'FCC Clear UI' button in Tools or run coverage again.ĭetails of how FCC is progressing with code coverage can be found in the Coverage Log tab in the Fine Code Coverage Tool Window with more detailed logs in the FCC Output Window Pane. This coverage is not dynamic and represents the coverage obtained from the last time you executed tests. The report shows line and branch coverage and risk hotspots with the facility to open your class files, that will have coloured margins to indicate uncovered or partially covered code. One of the 3 coverage tools provides the coverage results that are presented as a single unified report in the Fine Code Coverage Tool Window. Regardless of the coverage tool employed the process begins with FCC reacting to the test explorer in visual studio.

All of these settings are optional.įor options that have a project scope, these settings form a hierarchy where lower levels override or, for collections, override or merge with the level above. Thus you will find that there are separate configuration options for Ms coverage vs old coverage and options that are common to the two.Ĭonfiguration is ( mostly ) determined from Visual Studio options, finecodecoverage-settings.xml files and project msbuild properties. This abstraction does not work for MS code coverage. With the old coverage it was possible for FCC to provide an abstraction over each tool's exclusion / inclusion options. This will probably be the preferred coverage Microsoft now provides a free coverage solution that you can choose to use by setting the Visual Studio Fine Code Coverage enumeration option RunMsCodeCoverage. In previous releases there were two coverage tools being utilised, OpenCover and Coverlet that will be referred to as 'old coverage'. For instance, the NUnit Test Adapter extension is not sufficient.įine Code Coverage provides code coverage using one of 3 different coverage tools. Net - that the test adapters are nuget packages. Older versions can be obtained from here.įor. Download this extension from the Visual Studio Market Place ( vs 2019 ), Visual Studio Market Place ( vs 2022 )

Visual studio code coverage tool