coverlet VS RunCoverletReport

You might have noticed when you were looking in NuGet, there was a package called coverlet installed into the project:

There are a lot libraries to collect code coverage, one of this one is Coverlet: https://github.com/coverlet-coverage/coverlet

We use Coverlet. You have to do some work to get it working with your tests but I have no complaints. I don't know for sure if it works with VS Community, but since it plugs into MSBuild I'm not sure how it could be gated to that.

And I would like to build a total test coverage for the solution. So, I added coverlet.msbuild to the dependencies and executed the next command from the examples of coverlet

CoverletOutputFormat: The format of the report that coverlet will generate (opencover, cobertura, json). More here;

Utilize Coverletand Report Generator utilities – however, this is where its funny, because these are .NET CLI tools that need the .NET 6 SDK installed.

Coverlet works really well.

However, I am hesitant to do so. Whenever it seems I have to fight the tools that are provided for me this is a likely sign that I’m Doing Things Wrong because of some fundamental misunderstandings and misassumptions on my part. I did some digging and found that VSTest by design forces the placement of data collectors’ output into GUIDed subdirectories, see Coverlet documentation, Coverlet issue #500 and VSTest issue #2378. That this is forced by design reinforces my worries that I’m doing something counterproductive.

Coverlet

⚠️ Unfortunately, the Run Coverage Report extension still doesn't allow us to configure the coverlet parameters. There is an open pull request with this feature awaiting for approval here.