v3.1.12

Changes

• Fix: exclude test loggers from code coverage instrumentation. Fixes #64 and #72. Thanks to several community members for reporting the issue, sharing logs and validating workarounds.
• Fix: updated core testlogger to v3.1.140. Fixes spekt/xunit.testlogger#51.
• Infra: add docs for CircleCI. See https://github.com/spekt/junit.testlogger/blob/master/docs/circleci-recommendation.md and #68. Thanks @Peter-Darton-i2.

Nuget release: https://www.nuget.org/packages/JunitXml.TestLogger/3.1.12

v3.0.134

Changes

• Fix: escape illegal xml characters. Fixes #59. See spekt/testlogger#37
• Update to core test logger version 3.0.114

Nuget release: https://www.nuget.org/packages/JunitXml.TestLogger/3.0.134

v3.0.124

Changes:

• Update core testlogger to 3.0.86
• Fix: issue with numeral parsing in test name parser. See spekt/testlogger#35

v3.0.114

Changes:

• Update core testlogger to 3.0.78 for junit test adapter
• Replace Test Case name parser Possible Breaking Change
  • For most or maybe all users the new parser should fix the issues shown below, without introducing new issues. In case you do encounter any new parsing failures a feature flag Parser=Legacy has been added to use the prior parser. See logger config wiki for details.
  • Fix: Test case parse error if name contains special characters. See
    spekt/nunit.testlogger#90
  • Fix: Covers several parsing issues. Thanks @becha2 for all the detailed examples.
    spekt/testlogger#28
  • Fix: Log member data. Thanks @BottlecapDave for the issue report and @hach-que for the draft fix.
    #50
  • Fix: Issue parsing chars. Thanks @binarycow for the issue report.
    spekt/nunit.testlogger#90
  • Reduce log verbosity: The parser, if it encounters problems, will only output one warning per run to the console instead of one per problem

v3.0.110

Changes:

What's Changed

• Fix: Use parsed Method, not the test framework dependent name when building test output. Thanks @moly for the bug report. @Siphonophora in #45
• Fix issue with displaying parameterized test arguments for MSTest. Thanks @hoppities for the bug report and @CoskunSunali, @IshakAtLEGO for additional feedback. @Siphonophora in #46
• Fix issue with parsing char arguments in parameterized tests. @Siphonophora in #49

Full Changelog: v3.0.98...v3.0.110

v3.0.98

Changes:

• Fix: testsuite.time is now created using invariant culture, so it will no longer change depending on the culture of the system executing the tests.. #34 Thanks @thj-dk

v3.0.87

Changes:

• Refactor to support core testlogger.
• Compatibility: minimum framework is netstandard1.5 and TestPlatform 15.5.0
• Dropped support for outputting files as UTF8 with BOM. All files are now UTF8 only. Please open an issue if this is a breaking change for you.

v2.1.81

Changes:

• Prevent a false positive alert about invalid 'TargetFramework' command line argument. #31

Thanks to @gitfool for the pull request and to @moly and @alexpizarroj for submitting issues / feedback related to this release.

v2.1.78

Changes:

• Capture StdOut and StdErr into the JUnit report into the system-out and system-error elements at the bottom of the report. Note, the JUnit format does not offer a position to store the output directly in the testcase, which is why output is gathered at the bottom of the report. However, if you are using the FailureBodyFormat=Verbose option, then failed tests will have any output in their failure messages.
• Added a nuget package logo.
• Added ability to parse method names which include tuples or `'
• Fixed the hostname which now reports the machine name where the tests were run, instead of the test adapter.

Thank you to @IloSophiep, @jdelucaa, @tkohlmeier, @KonH, and @darrylmelander for submitting issues / feedback or code related to this release.

v2.1.32

Changes:

• Default xml encoding is now UTF8, instead of UTF8 with BOM. A new command line option exists to specify UTF8 with BOM if needed. #18
• Output now complies with the Ant Junit schema.
  • Timestamp field format was corrected . #17.
  • Time field format was corrected #16.
• Skipped tests now properly classified as skipped. #12

Thanks to @AnashOommen and @williamdenton for letting us know about the issues fixed in this release.