-
Notifications
You must be signed in to change notification settings - Fork 389
Could not find data collector 'XPlat Code Coverage' when targetting .dll #1118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you try with
As explained in guide for published project https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md |
Can you explain why I cant use `dotnet test` ?
[None of the examples here use](
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-test) `vstest` ?
Like i said, Im writing a tool that is supposed to let users execute any
test written by any test framework. My understanding was `dotnet test`
facilitated this.
dotnet/docs#14786 (comment)
…On Tue, Mar 16, 2021 at 7:26 PM Marco Rossignoli ***@***.***> wrote:
Can you try with
dotnet vstest bin/debug/netcoreapp3.1/test.dll --collect:\"XPlat Code
Coverage\"
As explained in guide for published project
https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABOPWTVV7ERJJICP76OXUUDTD4I2TANCNFSM4YZNACLA>
.
|
It's an implementation detail of test platform, we don't load collectors we implement one, you should open an issue and ask here https://github.com/microsoft/vstest/issues |
The solution is described here: #521 (comment) |
> dotnet add package coverlet.collector
dotnet test my.csproj --collect:\"XPlat Code Coverage\"
works. great!dotnet test bin/debug/netcoreapp3.1/test.dll --collect:\"XPlat Code Coverage\"
What am i missing here? Im writing a tool that integrates with coverage so i would like to support both scenarios.
The text was updated successfully, but these errors were encountered: