Closed
Description
openedon Mar 9, 2023
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Support-style question;customer needs help solving a problem [org][type][category]Support-style question;customer needs help solving a problem [org][type][category]