coverlet VS delivery-sdk-net

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

Delivery SDK

AppVeyor offers features such as .csproj files patching and AssemblyInfo patching. These features are not available in GitHub Actions and the easiest way to overcome this is to use parameters that the .NET CLI offers dotnet build -p:Version=1.2.3 and dotnet pack -p:PackageVersion=1.2.3 or dotnet pack -p:NuspecProperties="Version=1.2.3" if you use a .nuspec file.

To see the whole workflow in action, head to some of our SDK repos. You can also explore how we do releases using GitHub Actions. All code is in the workflows folder.