-
Notifications
You must be signed in to change notification settings - Fork 322
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
Lack of clear documentation for running tests with code coverage on MacOS #1053
Comments
As I understand right now coverage is only available on Windows. More info here #981 |
@a-h, @wli3 Code coverage is currently supported for Windows OS. On Windows OS, you can get Code Coverage for dotnet core test projects using As pointed out by @IvanAlekseev, support for Code Coverage in dotnet test for Windows OS is not yet there. |
Code Coverage is VS enterprise and windows only so far, current plan is to get the same level of support in dotnet test (windows + VS enterprise). Mac/linux support isn't in our immediate backlog. /cc @pvlakshm @sudiptadmsft to consider the feedback for prioritisation. |
Thanks for the clarification. |
Closing this as dupe of #981 |
From @a-h on September 7, 2017 18:32
I'm confused as to how to run unit tests with code coverage on Linux and OSX for .NET Core 2.0 projects using the built-in tools.
Steps to reproduce
dotnet new xunit
dotnet test
dotnet test --help | grep cover
dotnet vstest
or something.dotnet add package Microsoft.CodeCoverage
dotnet vstest ./bin/Debug/netcoreapp2.0/Updater.Tests.dll
dotnet vstest --collect:"Code Coverage" --framework:".NETCoreApp,Version=v2.0" ./bin/Debug/netcoreapp2.0/Updater.Tests.dll
Expected behavior
dotnet test --cover
and code coverage files would be output, and a summary table of results printed to the console.Actual behavior
Error message shown:
Then I find this comment:
#579 (comment)
I thought .NET Core was cross platform? I'm confused...
Environment data
dotnet --info
output:Copied from original issue: dotnet/cli#7612
The text was updated successfully, but these errors were encountered: