coverlet.msbuild 2.8.0 does not combine coverage when using MergeWith
See original GitHub issueDependabot pushed a number of updates to coverlet.msbuild to repositories I maintain just now to bump from 2.7.0 to 2.8.0, and for projects where code coverage is aggregated together using the MergeWith
MSBuild property, the stats are no longer being combined.
Here’s such an example PR: https://github.com/justeat/httpclient-interception/pull/171
This is causing builds to fail as their minimum coverage level specified by the Threshold
MSBuild property is now no longer being met.
Issue Analytics
- State:
- Created 4 years ago
- Comments:19 (2 by maintainers)
Top Results From Across the Web
coverlet.msbuild 2.8.0 does not combine coverage when ...
0, and for projects where code coverage is aggregated together using the MergeWith MSBuild property, the stats are no longer being combined.
Read more >Coverlet MSBuild Integration -Merging reports
This will create a coverage.json file that contains the code coverage report combining both tests project execution. You can also run dotnet test...
Read more >Dotnet Unit test with Coverlet- How to get coverage for ...
Instead, this is what I did. First, run dotnet test and tell coverlet to merge all your coverage results. (You need to reference...
Read more >Error running unit tests on azure devops with nugget ...
To generate json report(coverage.json): You should use coverlet.msbuild package with command dotnet test /p:CollectCoverage=true .
Read more >Where is the documentation to setup Code Coverage ...
Template for a good new topic, formatted with Markdown: ALM used (GitHub, Bitbucket Cloud, Azure DevOps) What is ALM?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes Azure DevOps also uses ReportGenerator internally to generate the coverage report.
Merging several files was always supported by ReportGenerator. You can give it a try.
And thanks for the advice we’ll keep more attention on versioning (related to missing breaking behavior)!