-
Notifications
You must be signed in to change notification settings - Fork 361
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
Support TRX test result format in test reporters #2161
Comments
Adding support for TRX files would significantly reduce our overhead when understanding test failures in Helix. Right now, engineers have to drill down through the |
@jonfortescue / @Chrisboh - you guys aware of this? Thoughts on next steps? |
We can add support for TRX files into Helix and get that work scheduled. @pakrym I do wonder though is this something that would meet your needs? According to @alexperovich you can just drop this with your run and it will produce the xunit output we would need. |
Added to the Helix go-live Epic. Please move as appropriate as I can appreciate how this might be more urgent. |
Issue moved to dotnet/core-eng #5655 via ZenHub |
dotnet vstest
/dotnet test
doesn't support producing xUnit XML.It would be nice to be able to ingest TRX result files.
cc @alexperovich @anurse
The text was updated successfully, but these errors were encountered: