-
Notifications
You must be signed in to change notification settings - Fork 15
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
JUnit results file missing on MacOS when code coverage collector is used #72
Comments
@ablok I don't have access to a MacOS box. I can validate that TestResults.xml is created on Linux. Would it be possible to share a trace log? https://github.com/microsoft/vstest/blob/main/docs/diagnose.md#collect-traces-using-command-line |
@codito here is the output from the log.datacollector.24-02-09_13-09-43_24858_5.txt |
Thanks @ablok, the logs helped! I think we need to apply a fix to exclude all Spekt* assemblies from code coverage, the Code Coverage instrumentation is messing up test result callbacks and hence we never get a call back to save the run results. Workaround
|
@codito the workaround indeed works. |
Fix released with https://www.nuget.org/packages/JunitXml.TestLogger/3.1.12 |
When running a dotnet test command using
--logger "jUnit"
, aTestResults.xml
file will be created. However, when adding the--collect "Code Coverage"
option, theTestResults.xml
file will no longer be created. This happes on MacOS. On Windows the file will be created as expected.I created a sample project here: https://github.com/ablok/JunitLoggerExample
The text was updated successfully, but these errors were encountered: