You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+2-4
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ When not using Microsoft.TestingPlatform you have added test adapters through nu
27
27
28
28
Fine Code Coverage provides code coverage using one of 3 different coverage tools. In previous releases there were two coverage tools being utilised, OpenCover and Coverlet that will be referred to as 'old coverage'.
29
29
Microsoft now provides a free coverage solution that you can choose to use by setting the Visual Studio Fine Code Coverage enumeration option RunMsCodeCoverage. This will probably be the preferred coverage
30
-
tool for most developers. It is currently in Beta.
30
+
tool for most developers.
31
31
32
32
With the old coverage it was possible for FCC to provide an abstraction over each tool's exclusion / inclusion options. This abstraction does not work for MS code coverage.
33
33
Thus you will find that there are separate configuration options for Ms coverage vs old coverage and options that are common to the two.
@@ -109,8 +109,6 @@ The old coverage was based upon every test. Ms code coverage is coverage from th
109
109
110
110
## How to utilize MS Code Coverage with FCC ?
111
111
112
-
Firstly you need to change the RunMsCodeCoverage option from No.
113
-
114
112
Ms code coverage requires a [runsettings](https://docs.microsoft.com/en-us/visualstudio/test/configure-unit-tests-by-using-a-dot-runsettings-file?view=vs-2022) file that is configured appropriately for
115
113
code coverage. This requires that you have the ms code coverage package and have pointed to it with the TestAdaptersPaths element as well as specifying the ms data collector. [Exclusions and inclusions](https://docs.microsoft.com/en-us/visualstudio/test/customizing-code-coverage-analysis?view=vs-2022#include-or-exclude-assemblies-and-members)
116
114
are also specified in the runsettings. I don't think that the documentation is clear enough on how this works so you may want to look at [this issue](https://github.com/microsoft/vstest/issues/3462).
@@ -349,7 +347,7 @@ If you are using option 1) then project and global options will only be used whe
349
347
| DisabledNoCoverage | Set to false for VS Option Enabled=false to not disable coverage |
350
348
| RunWhenTestsFail | By default coverage runs when tests fail. Set to false to prevent this. **Cannot be used in conjunction with RunInParallel**|
351
349
| RunWhenTestsExceed | Specify a value to only run coverage based upon the number of executing tests. **Cannot be used in conjunction with RunInParallel**|
352
-
| RunMsCodeCoverage | Change to IfInRunSettings to only collect with configured runsettings. Yes for runsettings generation. |
350
+
| RunMsCodeCoverage | Change to IfInRunSettings to only collect with configured runsettings. Yes (default) for runsettings generation. No to use Coverlet or OpenCover. |
353
351
| IncludeTestAssembly | Specifies whether to report code coverage of the test assembly |
354
352
| IncludeReferencedProjects | Set to true to add all directly referenced projects to Include. |
355
353
| IncludeAssemblies | Provide a list of assemblies to include in coverage. The dll name without extension is used for matching. |
0 commit comments