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
Is your feature request related to a problem? Please describe.
The new .NET 7 doesn't seem to accept MSBuild coverage flags like in .NET 6 when I call my xUnit tests like this:
dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=lcov /p:CoverletOutput=lcov.info
This only generates a coverage.json file instead of the lcov.info file.
Describe the solution you'd like
Add support for parsing / converting the coverage.json file format in coverage gutters.
Describe alternatives you've considered
Adding a middleware as a build job that does the conversion like this guy. But I really didn't like the thought.
Additional context
I can provide a coverage.json file if you need to figure out what the format even is.
The text was updated successfully, but these errors were encountered:
Hey @Bonifatius94
this is an open issue .net 7.0-rc.1 and later. See microsoft/vstest#4014. From the commentary on various issues this will be fixed before the release.
Thanks for the issue @Bonifatius94 and thanks for the extra info and workaround @aburgett87 (I am not familiar with the .Net space so I am glad you could assist!).
We can leave this closed for now but don't hesitate to reopen or create a new issue if the 7 release starts causing you issues.
Is your feature request related to a problem? Please describe.
The new .NET 7 doesn't seem to accept MSBuild coverage flags like in .NET 6 when I call my xUnit tests like this:
dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=lcov /p:CoverletOutput=lcov.info
This only generates a coverage.json file instead of the lcov.info file.
Describe the solution you'd like
Add support for parsing / converting the coverage.json file format in coverage gutters.
Describe alternatives you've considered
Adding a middleware as a build job that does the conversion like this guy. But I really didn't like the thought.
Additional context
I can provide a coverage.json file if you need to figure out what the format even is.
The text was updated successfully, but these errors were encountered: