- Update core testlogger to 3.1.140.
- Fix: exclude code coverage instrumentation for test loggers. See spekt/junit.testlogger#64 and spekt/junit.testlogger#72.
- Fix for reporting nested test classes. See #48 and spekt/testlogger#41. Thanks @pageyboy.
- Update core testlogger to 3.1.138.
- Infra: fix build when repo is cloned in path with whitespace.
- Update core testlogger to 3.1.130.
- Fix for illegal xml characters in various names. See spekt/testlogger#37
- Use DisplayName for method names. See #46
- Various infra fixes: move to net7.0, add github CI and remove appveyor.
- Update core testlogger to 3.0.86 for xunit test adapter
- Fix: Explicit tests should be marked as Skipped. See https://github.com/spekt/nunit.testlogger/issues/86
- 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=Legacyhas been added to use the prior parser. See logger config wiki for details. - Fix: Test case parse error if name contains special characters. See https://github.com/spekt/nunit.testlogger/issues/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. spekt/junit.testlogger#50
- Fix: Issue parsing chars. Thanks @binarycow for the issue report. https://github.com/spekt/nunit.testlogger/issues/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
- Fix: Issue parsing numbers. See spekt/testlogger#35
- 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
- Upgrade testlogger to 3.0.47
- Fix: generate test results when used along with JUnit.TestLogger. See https://github.com/spekt/xunit.testlogger/issues/36 and https://github.com/spekt/xunit.testlogger/issues/37
- Upgrade testlogger to 3.0.31
- Fix: overwrite test result file if it already exists. See https://github.com/spekt/nunit.testlogger/issues/76
- Remove unused code from refactoring. See #31
- Ensure Traits for Tests are available in the report. Use
TestResultInfo.TestCase.Traitsinstead ofTestResultInfo.Traits. See #32
- Refactor to support core testlogger
- Compatibility: minimum framework is netstandard1.5 and TestPlatform 15.5.0
- Use test run start and end times for run duration reporting for assembly. See #26
- Escape control characters from the generated xml. See #25
- Token expansion for
{assembly}and{framework}in results file. See https://github.com/spekt/testlogger/wiki/Logger-Configuration