NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #2043 most downloaded on NuGet
Transforms XML from trx-Testresults to JUnit-Testresults / trx to JUnit XML
Latest stable
2.1.0
Last release 3 years ago
no release in 18 months
Release timing varies
gaps range from 9 days to 1.5 years
Nearly every release is documented
notes for 23 of 24 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
24 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Core-project can be used standalone, so respect potential use outside of trx2junit
https://www.nuget.org/packages/trx2junit/2.1.0
Full Changelog: https://github.com/gfoidl/trx2junit/compare/v2.0.4...v2.1.0
Incorrect testcase names in xml
https://www.nuget.org/packages/trx2junit/2.0.4
Full Changelog: https://github.com/gfoidl/trx2junit/compare/v2.0.3...v2.0.4
Timestamps honor timezone Pt. 2
Your coding agent can read these notes before it upgrades. Set up the MCP server →
https://www.nuget.org/packages/trx2junit/2.0.3
Full Changelog: https://github.com/gfoidl/trx2junit/compare/v2.0.2...v2.0.3
Opt-in to emit error message in CDATA-element of failure-element
https://www.nuget.org/packages/trx2junit/2.0.2
Full Changelog: https://github.com/gfoidl/trx2junit/compare/v2.0.1...v2.0.2
Removed console usage in worker -- emit event instead
https://www.nuget.org/packages/trx2junit/2.0.1
Full Changelog: https://github.com/gfoidl/trx2junit/compare/v2.0.0...v2.0.1
Created standalone package of Core-logic and dropped .NET Core 2.1
Rollforward policy Major is applied, in order to be more future proof.
The core-logic is split out into a separate packe trx2junit.Core which can be used conversion with a custom host / tool.
The tool trx2junit itself is a consumer of this package.
From the point of view of trx2junit it's just a refactoring, usage didn't change.
.NET Core 2.1 reached end of life on 21.08.2021, so it's support got dropped here. If you're still using .NET Core 2.1, so just don't update to this version. Stay on the v1.x versions. If there should should be any bug, please still file an issue, so it can be fixed and potentially backported to a new v1.x release.
I'm aware that there are more crucial contributors for perf, like reading and writing XML, but I love vectors and vectorized code. Therefore just for fun https://github.com/gfoidl/trx2junit/pull/64 was done.
The vectorized parts are disabled by default, and hidden behind a feature-toggle that can be enabled by setting the environment variable TRX2JUNIT_VECTORS_ENABLED to any non-empty value.
Basically I didn't want to merge that PR, but due the refactorings of https://github.com/gfoidl/trx2junit/pull/93 it wouldn't be managable anymore. So the (better) variant to integrate in the main-branch, and hide behind a feature-toggle was chosen.
https://www.nuget.org/packages/trx2junit/2.0.0
Full Changelog: https://github.com/gfoidl/trx2junit/compare/v1.6.0...v2.0.0
https://www.nuget.org/packages/trx2junit/1.6.0
https://www.nuget.org/packages/trx2junit/1.6.0
Jenkins-JUnit emit status attribute for testcase
For Jenkins JUnit on the testcase the status-attribute is set. By default 1 is set for success, and 0 for failure.
This can be configured via environment variables (note: if omitted, the default values will be used):
| Status | Variable | default value |
|---|---|---|
| success | TRX2JUNIT_JENKINS_TESTCASE_STATUS_SUCCESS |
1 |
| failure | TRX2JUNIT_JENKINS_TESTCASE_STATUS_FAILURE |
0 |
| skipped | TRX2JUNIT_JENKINS_TESTCASE_STATUS_SKIPPED |
not set |
https://www.nuget.org/packages/trx2junit/1.5.0
Relax trx2junit to allow test-method w/o name-attribute
https://www.nuget.org/packages/trx2junit/1.4.1
Support for .NET 5.0 (#79, #80)
https://www.nuget.org/packages/trx2junit/1.4.0
TrxTestResultXmlParser can read more result types
https://www.nuget.org/packages/trx2junit/1.3.2
trx to junit keeps stdout per testcase
https://www.nuget.org/packages/trx2junit/1.3.1
rewritten some of the guts -- especially the parsers and builders -- as prerequisite for adding #60
--junit2trx added (https://github.com/gfoidl/trx2junit/issues/60)https://www.nuget.org/packages/trx2junit/1.3.0
https://www.nuget.org/packages/trx2junit/1.2.6
https://www.nuget.org/packages/trx2junit/1.2.6
trx2junit v1.2.5 adds (preview) support for .NET Core 3.0. It can run on .NET Core Runtime 3.0.0-preview6-27804-01 and newer.
trx2junit v1.2.5 adds (preview) support for .NET Core 3.0. It can run on .NET Core Runtime 3.0.0-preview6-27804-01 and newer.
.NET Core 2.1, .NET Core 2.2 aren't affected by this change, and will run as always.
With the .NET Core 3.0 support you can use trx2junit for your projects that target .NET Core 3.0 (preview).
https://www.nuget.org/packages/trx2junit/1.2.5
TestDefinitions with multiple UnitTestResults not recognized correclty
https://www.nuget.org/packages/trx2junit/1.2.4
Test count for separate test suites are being combined
https://www.nuget.org/packages/trx2junit/1.2.3
Run trx2junit with file parameter returns "Path cannot be empty string or whitespaces"
https://www.nuget.org/packages/trx2junit/1.2.2
NUnit trx-output with no / empty tests results in exception
https://www.nuget.org/packages/trx2junit/1.2.1
ability to output results to a different folder
https://www.nuget.org/packages/trx2junit/1.2.0
multiple trx-files can be handled
https://www.nuget.org/packages/trx2junit/1.1.0
https://www.nuget.org/packages/trx2junit/1.0.2
https://www.nuget.org/packages/trx2junit/1.0.2
Nothing published for this version
Initial release as _.NET global tool_
Initial release as .NET global tool
https://www.nuget.org/packages/trx2junit/1.0.0
One column per quarter.