coverlet.msbuild not working on .net 7

[maricomic]

Coverlet.msbuild (3.1.2) not working on .net 7

dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=opencover /p:MergeWith="../CoverageResults/coverage.json"

Version .net: 7.0.100-rc.2.22477.23

[aburgett87]

Hey @maricomic
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.

The workaround is to use environment variables.

[thinkbeforecoding]

I have this problem with the net7.0 release.
What is the new official way to pass msbuild parameters for tests ?

[azchohfi]

Also hitting this.

[GeorgDangl]

Hitting the same, just tried to upgrade a library project to .NET 7 and it failed to generate coverage.

We're using https://github.com/nuke-build/nuke, so it was actually quite easy to resolve, but it looks really bad:

DotNetTest(c => c
    .EnableCollectCoverage()
    // See https://github.com/coverlet-coverage/coverlet/issues/1391, MSBuild parameters
    // in .NET 7 need to be set via environment variables
    .SetProcessEnvironmentVariable("CollectCoverage", "true")
    .SetCoverletOutputFormat(CoverletOutputFormat.cobertura)
    .SetProcessEnvironmentVariable("CoverletOutputFormat", "cobertura")

[andmos]

I'm also seeing this - using

dotnet test BikeshareClient/TestBikeshareClient/TestBikeshareClient.csproj /p:CollectCoverage=true /p:Threshold=80 /p:ThresholdType=line /p:CoverletOutputFormat=opencover /p:ExcludeByAttribute=ExcludeFromCodeCoverageAttribute

With the msbuild plugin. No coverage shows up, just the standard output:

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.

Passed!  - Failed:     0, Passed:    98, Skipped:     0, Total:    98, Duration: 14 s

[jmoralesv]

Hi all, I'm reporting the same, with the .NET 7 SDK released early this week and using Azure Pipelines and coverlet.msbuild version 3.2.0.

dotnet test --configuration $(BuildConfiguration) /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura

I can confirm that using environment variables in Azure Pipelines works, by using the PowerShell task: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/set-variables-scripts?view=azure-devops&tabs=powershell

Thanks @GeorgDangl for the suggestion!

As I have several projects already configured for coverlet.msbuild, I'll wait until there is a solution for this issue with .NET 7.

[mtelle]

Hi, for the people could not wait for release 7.0.101. I was able to build the fixed version of dotnet.dll.
You can download from: Here
Just copy it in C:\Program Files\dotnet\sdk\7.0.100 and now it will work.

[mu88]

Another option is to add the necessary properties to csproj/Directory.Build.props, e. g.:

<PropertyGroup Condition="$(MSBuildProjectName.Contains('.Tests.'))">
  <CollectCoverage>true</CollectCoverage>
  <ExcludeByAttribute>GeneratedCodeAttribute</ExcludeByAttribute>
  <Exclude>[*]*.Migrations.*</Exclude>
  <ExcludeByFile>**/MyFile.cs</ExcludeByFile>
  <CoverletOutputFormat>opencover</CoverletOutputFormat>
</PropertyGroup>

[jmoralesv]

Hi all,
I'm writing to report that, after upgrading to version 7.0.101 of the .NET 7 SDK which was released yesterday, I was able to remove the workaround (using environment variables to set the coverlet parameters) and get the coverlet test results with the parameters specified in dotnet test.

dotnet test --configuration $(BuildConfiguration) /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura

I tested in my Azure DevOps pipelines and works as expected.

Now I can roll the upgrade to .NET 7 to all my personal projects 🎉

[samsmithnz]

Is there any disadvantage to keeping the -e parameters to set the environment variables? I've updated 40+ projects...

[jmoralesv]

Is there any disadvantage to keeping the -e parameters to set the environment variables? I've updated 40+ projects...

I don't think there is any disadvantage, the only question is whether the environment variables approach has precedence over the ones passed as parameters of dotnet test.

[daveMueller]

Hi all, the issue was fixed by the microsoft guys with sdk 7.0.101 that was released last week microsoft/vstest#4014. I just checked it with a repro from another related issue and it works fine. Please give it a try again. Thanks @jmoralesv for already mentioning it.

[daveMueller]

I close this as the external issue is fixed. Feel free to reopen.