Release 2.0.1

Add 'github' as format option, because markdown on github can not render html and markdown somewhere else can rather handle html then latex

Version 2.0.0

Fix issue #65: 'Session-level issues' / 'Issues recorded without an associated test or suite' are now listed in test results

Version 2.0.0-beta

Replace XCResultKit usage with direct xcresulttool and xccov parsing using local Codable models.
Remove XCResultKit as a package dependency from Package.swift.
Migrate JUnit, summary/test formatting, coverage formatting, and issues JSON paths to the new model/tooling layer.
Keep output compatibility where possible while aligning with modern xcresulttool payloads.
Raise the minimum supported platform to macOS 12.
Keep expected failures as a distinct state in human-readable outputs, while emitting them as passing test cases in JUnit/Sonar XML for compatibility.
Treat unknown --coverage-targets values as an error instead of silently producing empty coverage output.

Version 1.9.4

Previously, we were only ever parsing the first failure for a test and passing that to the JUnit representation.
However, a test might contain multiple failures and this is fully supported by the JUnit spec.
To fix the issue, we'll collect all failures from the XCResult file and pass them to the JUnit result a list.
This will prevent us from losing important diagnostic information from the test result.
Credit for this change goes to Gordon Fontenot.

Release 1.9.3

Undo the last change quoting the grep parameters, doesn't work. Duh!

Release 1.9.2

Fix grep call for zsh

Release 1.9.1

Fix testclass path search pattern to include structs, which can be used with swift testing

Release 1.9.0

Add flag to ignore all pathnames which do not contain projectRoot (if any) in coverage reports

In coverage reports it can now be prevented to list files from swift packages.
Convert tests to Swift Testing in order to use tests with parameters easier.

Release 1.8.5

Fix incorrect JUnit failure message for merged & repeated test case (Merits go to John Szumski)
Fix short message and type not populated for junit output (Merits go to Luis Padron)

Release 1.8.4

Add 'configuration' property to test export.

Instead of:

<testExecutions version="1">
	<file path="TestFile_1">
		<testCase name="test1()" duration="20517"/>
	</file>
	<file path="TestFile_1">
		<testCase name="test1()" duration="20517"/>
	</file>
</testExecutions>

the different test runs (or "configurations" in Xcode lingo) are now distinguishable.

<testExecutions version="1">
	<file path="TestFile_1" configuration="iPhoneTests">
		<testCase name="test1()" duration="20517"/>
	</file>
	<file path="TestFile_1" configuration="iPadTests">
		<testCase name="test1()" duration="20517"/>
	</file>
</testExecutions>