NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet · #2051 most downloaded on NuGet
Transforms XML from trx-Testresults to JUnit-Testresults / trx to JUnit XML
Last release 3 years ago
no release in 18 months
Release timing varies
gaps range from 9 days to 1.5 years
Some releases are documented
notes for 10 of 24 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
24 releases · first in 2018
Core-project can be used standalone, so respect potential use outside of trx2junit
https://www.nuget.org/packages/trx2junit/2.1.0
Full Changelog: v2.0.4...v2.1.0
Incorrect testcase names in xml
https://www.nuget.org/packages/trx2junit/2.0.4
Full Changelog: v2.0.3...v2.0.4
One column per quarter.
Timestamps honor timezone Pt. 2
https://www.nuget.org/packages/trx2junit/2.0.3
Full Changelog: 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: 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: 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 #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 #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: v1.6.0...v2.0.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 |
Relax trx2junit to allow test-method w/o name-attribute
Support for .NET 5.0 ( #79 , #80 )
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →