Releases: gfoidl/trx2junit
v2.1.0
Fixed 🐛
- Core-project can be used standalone, so respect potential use outside of trx2junit (#116)
What's new?
Where to get?
https://www.nuget.org/packages/trx2junit/2.1.0
Full Changelog: v2.0.4...v2.1.0
v2.0.4
Fixed 🐛
- Incorrect testcase names in xml (#110)
Where to get?
https://www.nuget.org/packages/trx2junit/2.0.4
Full Changelog: v2.0.3...v2.0.4
v2.0.3
Fixed 🐛
- Timestamps honor timezone Pt. 2 (#109)
Where to get?
https://www.nuget.org/packages/trx2junit/2.0.3
Full Changelog: v2.0.2...v2.0.3
v2.0.2
What's new
- Timestamps honor timezone (#107)
- Opt-in to emit error message in CDATA-element of failure-element (#108)
Where to get?
https://www.nuget.org/packages/trx2junit/2.0.2
Full Changelog: v2.0.1...v2.0.2
v2.0.1
Fixed 🐛
- Removed console usage in worker -- emit event instead (#98)
- JUnit: emit failure content with message as CData element (#101)
- Fixed XUnit's testcase name to be not the full-qualified name (#103)
Where to get?
https://www.nuget.org/packages/trx2junit/2.0.1
Full Changelog: v2.0.0...v2.0.1
v2.0.0
What's new
- Apply RollForward policy (#91)
- Created standalone package of Core-logic and dropped .NET Core 2.1 (#93)
Apply RollForward policy
Rollforward policy Major is applied, in order to be more future proof.
Created standalone package of Core-logic
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.
Dropped .NET Core 2.1
.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.
Vectorization Part I
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.
Where to get?
https://www.nuget.org/packages/trx2junit/2.0.0
Full Changelog: v1.6.0...v2.0.0
v1.6.0
v1.5.0
What's new
- Jenkins-JUnit emit status attribute for testcase (#84)
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 |