Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support TRX test result format in test reporters
See original GitHub issuedotnet vstest/dotnet test doesn’t support producing xUnit XML.
It would be nice to be able to ingest TRX result files.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Add support for test results in .TRX format · Issue #424
Currently you can not build the report from TRX test results. What is the expected behavior? An ability to build Allure report from...
Read more >How do I format Visual Studio Test results file (.trx) into a ...
Since this file is XML you could and should use xsl to transform it to another format. The IAmUnkown - blog has an...
Read more >Support .NET unit test results directly (#28798) · Issues
Software development teams who want to see unit test results output in .trx format. This is a feature that directly impacts the day...
Read more >PublishTestResults@2 - Publish Test Results v2 task
This file contains the instructions to build code and run tests. The tests are then copied to a file testresults.trx inside the container....
Read more >Collect test data
NET Core trx output to XML format. A working .circleci/config.yml section might look like this: steps: - ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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
mc.dot.netscreens and it’s very time consuming (and mostly impenetrable for external contributors). This is a high priority for our Helix adoption in ASP.NET (cc @Eilon).Issue moved to dotnet/core-eng #5655 via ZenHub