Solution for a parallel tests launching

[ivangrebeniuk]

Feature request

Solution to run UI test in parallel mode and use SimctlCLI

Describe the solution you'd like

First of all I'd like to thank you for SwiftSImctlCLI tool, it's great and handy, thanks!
SimctlCLI locally works awesome, but I've faced with an issue when launching tests on CI with parallel mode:
I run UI tests in parallel mode, 6 simulators simultaneously to speed up the process, for this purpose we use Teamcity + Fastlane and native XCUITests. In this case SimctlCLI does not work and all tests fail with an error, I suppose it happens because every simulator has it's own device ID.
If I run my tests on CI without parallelisation, in this case SimctlCLI works as expected and tests are passed successfully.
Are there any solutions to use SimctCLI with parallel launching? If it is somehow possible, it would be great to add description of this feature to the documentation.
If it's not possible now, how do you think about implementing support of parallel testing?

Additional context

Thank you!

[jkuchar]

As parallel run is default, when you set up UI tests I had run into the issue and found solution, that is surprisingly straightforward! cc @ctreffs

The Problem

The whole thing is almost ready for parallel testing. There is just need to provide correct --set testing to xcrun and it will start working. :)

The Solution

Server listening on port 50430...
Command: xcrun simctl --set testing uninstall 7B250A2C-488B-4783-BCB8-C76A97F9E3EB com.ivyassistant.ivy.mobile.ios
Success: 

The Fix

The best way would be to have some kind of parallel parameter, which changes the --set which is used with simctl tool for parallel cloned devices.

I'm not good in the Swift development but at least I have found the fix, that will make the whole tool to work with parallel environment (unfortunately stops working with the serial one).

There need to provide parameter for binary OR configuration if in SwiftClient OR detecting evenironment and passing the information over the HTTP parameter.

I will provide draft fix in PR (here is the key)