Open dazinator opened 2 years ago
You should check with the diagnostics enabled https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/Troubleshooting.md#collectors-integration and look at what coverlet is filtering out.
Please use .runsettings for your test see https://github.com/Bertk/coverlet/blob/master/Documentation/VSTestIntegration.md#advanced-options-supported-via-runsettings
or CLI parameter DataCollectionRunSettings.DataCollectors.DataCollector.Configuration.Exclude similar to https://github.com/Bertk/coverlet/blob/master/Documentation/VSTestIntegration.md#passing-runsettings-arguments-through-commandline
This issue is stale because it has been open for 3 months with no activity.
Please verify whether the problem still exists using the latest coverlet 6.0.2 release.
My xunit tests projejct references by backend asp.net core project, which hosts a front end blazor (wasm) project (and hence has a reference to it)
I am attempting to exclude this blazor project from code coverage.
The test is run via an azure devops yaml:
However after this runs, and I look at the report uploaded to devops, it still shows me types in the Foo.Client assemlby:
The exclude pattern appears correct to me, am I doing something wrong?