In our CI environment our xcresult files contain two "Actions" as we test on two distinct devices.
We recently had a case where a PR failed on the second of those devices, but passed on the first. This resulted in the xcresultparser output summary containing "Number of failed tests = 1" but the detail contained no test failures.
This change resolves this by enumerating all actions when generating the detail. To disambiguate, the run destination eg "iPhone 14 Pro" is displayed alongside the target name.
I'm happy to take feedback and evolve this change. I appreciate outputting the run destination is a functional change. I considered making it opt-in behind a cli flag; but also think it's reasonable to display it always.
In our CI environment our xcresult files contain two "Actions" as we test on two distinct devices.
We recently had a case where a PR failed on the second of those devices, but passed on the first. This resulted in the xcresultparser output summary containing "Number of failed tests = 1" but the detail contained no test failures.
This change resolves this by enumerating all actions when generating the detail. To disambiguate, the run destination eg "iPhone 14 Pro" is displayed alongside the target name.
I'm happy to take feedback and evolve this change. I appreciate outputting the run destination is a functional change. I considered making it opt-in behind a cli flag; but also think it's reasonable to display it always.