You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running tests against multiple destinations (e.g. iOS 8 + 9 simulators), xcodebuild produces a separate TestSummaries.plist for each destination. It would be super cool to aggregate these into a single JUnit report.
I propose flattening all the test runs into a single array of testsuites in the resulting XML. If we do that, we'll need to have some metadata at the testsuite level to distinguish one run of a target from another on a different destination.
Using a properties element allows us to add arbitrary key-value pairs to the testsuite.
The text was updated successfully, but these errors were encountered:
When running tests against multiple destinations (e.g. iOS 8 + 9 simulators), xcodebuild produces a separate TestSummaries.plist for each destination. It would be super cool to aggregate these into a single JUnit report.
I propose flattening all the test runs into a single array of
testsuites
in the resulting XML. If we do that, we'll need to have some metadata at thetestsuite
level to distinguish one run of a target from another on a different destination.Using a
properties
element allows us to add arbitrary key-value pairs to thetestsuite
.The text was updated successfully, but these errors were encountered: