.runsettings Data Collector not being applied in CLI

[Creastoff]

When you run dotnet test .\XUnitTest.sln -s .\XUnitTest\.runsettings against this example solution and import the code coverage results into Visual Studio 2022 Enterprise you can see references to unwanted binaries, i.e. Moq.dll. When you use the same .runsettings via Visual Studio's "Analyze Code Coverage" functionality you can only see references to the binaries generated by the build.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 61ca4064-7481-a263-60fc-c70127f2ad16
• Version Independent ID: 2878af44-8208-7bd8-46d4-3acda3e82ce0
• Content: dotnet test command - .NET CLI
• Content Source: docs/core/tools/dotnet-test.md
• Product: dotnet-fundamentals
• Technology: dotnet-cli
• GitHub Login: @tdykstra
• Microsoft Alias: tdykstra

[tdykstra]

@nohwnd Can you help with this?

[Creastoff]

@tdykstra @nohwnd Has this slipped the net due the the "not triaged" label being removed?

[nohwnd]

@jakubch1 please help :)

[jakubch1]

Currently you have to create runsettings and exclude libraries (https://learn.microsoft.com/en-us/visualstudio/test/customizing-code-coverage-analysis?view=vs-2022)
In VS it is done automatically as we know all projects in the solution. In command line we don't have this knowledge.
We will work on simplifying this: microsoft/codecoverage#12

[jakubch1]

Please change runsettings exclusions to:

								<ModulePath>.*xunit.execution.dotnet.dll$</ModulePath>
								<ModulePath>.*xunit.runner.visualstudio.dotnetcore.testadapter.dll$</ModulePath>
								<ModulePath>.*xunit.runner.utility.netcoreapp10.dll$</ModulePath>
								<ModulePath>.*xunit.assert.dll$</ModulePath>
								<ModulePath>.*unittests.dll$</ModulePath>
								<ModulePath>.*xunit.core.dll$</ModulePath>
								<ModulePath>.*humanizer.dll$</ModulePath>
								<ModulePath>.*xunit.runner.reporters.netcoreapp10.dll$</ModulePath>
								<ModulePath>.*moq.dll$</ModulePath>