Releases: a7ex/xcresultparser
Release 1.7.2
Release 1.7.1
- revert changes to Package.swift so we can build with Xcode 15 again
Release: 1.7.1-prerelease-2024-07-30
Full Changelog: 1.7.0...1.7.1-prerelease-2024-07-30
- Fixes compilation with Xcode 15.4
- Fixes unit test on GitHub CI
Release 1.7.0
New version 1.7.0 is now Xcode 16 compatible.
The xcresulttool command line tool, which comes with the developer tools of Xcode 16, changed the API. And so the Swift Package XcresultKit had to be updated.
Release 1.6.5
Changed the Junit xml slightly in order to be compatible with Jenkins plugin
It looks like the Jenkins plugin (https://plugins.jenkins.io/xunit/) expects:
only 3 decimal places after the . in the time attribute
an errors attribute, even if errors=0 on the testsuite
Release 1.6.4
removed swiftlint plugin from Package.swift file, as it seems to not work with commandline tools?
Release 1.6.3
Reverted swift package version back to 5.6
Fixed bug introduced in last version, which broke unit tests as well
Release 1.6.2
Fix crash for cobertura coverage converter
The DTD URL changed and the fallback file, which was supposed to be read from the bundle crashed the app.
No surprise, because the command line tool is not a bundle. DUH!
The fix is to include the DTD as string in the code. Also removed the online poll of the DTD, as it will probably never change!
Release 1.6.1
Add parameter to define the detail level of the coverage information
Thanks to @nkokhelox for implementing four levels of granularity for the coverage data output: methods, classes, targets, totals
Release 1.6.0
Use new command of Apple's xccov tool to speed up execution, when computing the code coverage significantly.
Before that the coverage for each code file had to be queried one by one. Now with the new xccov tool from Xcode 15 only one command and a little bit of JSON parsing is required. That is a huge performance improvement.
Add new commands to export warnings and errors in a format suitable for Gitlab Code Climate support.
Fix a bug, where code coverage executionCount would always only be one digit long.