Difference in coverage results between Windows and Linux

[ArturDorochowicz]

I'm getting different coverage results between Windows and Linux.

In a .net solution with references: Test Project -> ProjectA -> Project B, if tests in Test Project don't exercise anything from Project B, then on Linux Project B is not included in coverage results, but it is included (with 0 coverage as expected) when run on Windows.

I've checked this with .Net 7 and Microsoft.NET.Test.Sdk 17.5.0, as well as with .Net 6 and Microsoft.NET.Test.Sdk 17.6.3.

I'm attaching a tiny solution (projects: Tests -> Console -> Library) that shows the problem Project.zip. For this solution I get (note missing library.dll in Linux results):
on Linux:

on Windows:

In both cases the coverage was obtained with: dotnet test --collect "Code Coverage"

[jakubch1]

@ArturDorochowicz thank you for reporting this issue. The root cause for this discrepancy is that on Windows by default we enable only dynamic instrumentation and on linux we have both dynamic and static instrumentation enabled. I am working on making it consistent.

[jakubch1]

I've fixed issue. It will be available in 17.8.0 release. If you want you can use preview package: https://dev.azure.com/dnceng/public/_artifacts/feed/test-tools/NuGet/Microsoft.NET.Test.Sdk/overview/17.8.0-preview-23363-04