Good to hear. Parallel iOS testing with appium still holds good with official Appium 1.6 release? Also we are supposed to start ios-webkit-debug-proxy for each device right! are you starting with different ports?
This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
1 month later
@sugatmankar: How to do parallel execution in iOS 10.2 devices with Appium 1.6.3
9 days later
@VikramVI I figured it out
@sugatmankar if i provide wdaPort as caps i see the app launching parallel, but the tests run in sequence
[debug] [XCUITest] Starting iproxy to forward traffic from local port 63709 to device port 8100 over USB
When you run your tests can u see what the iproxy forward traffic port is
@saikrishna321: Can you please provide the command that you use for starting appium session
@pavanbachu i got it running in parallel they are extremely close though
Hello Guys,
I mentioned for 10.X version only and please always use updated appium from its source. Rest thing about invoking parallel test is up to you ie use cucumber jvm parallel plugin or TestNG for invoking test cases, or launch one by one by changing device id manually. Hope you enjoyed working on iOS 
always changing , its better to say always challenging if you are not aware its changes.
@pavanbachu nope, i have build this framework AppiumTestDistribution which takes of parallel run
15 days later
@sugatmankar
Was able to start Appium instance at different port , but iproxy local port seems to 8100 for both runs. So one of the them throws error ..
[XCUITest] Error: iproxy exited with code '208'
at SubProcess. (../../lib/webdriveragent.js:438:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (../../lib/teen_process.js:197:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess.handle.onexit (internal/childprocess.js:215:12)
Error: iproxy exited with code '208'
at SubProcess. (../../lib/webdriveragent.js:438:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (../../lib/teen_process.js:197:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess.handle.onexit (internal/childprocess.js:215:12)
@saikrishna321 : How were able to spin iproxy at port 63709 which is by default 8100.. ?
Hi everyone, how's the parallel tests running on real iOS device on the latest 1.6.4 beta version of appium? Have you guys tried?
19 days later
@alangithubtrader have tried the parallel run on 1.6.4 beta and it runs perfectly.
Can you elaborate how you architected it? Did you use ci such as Jenkins plus selenium grid? And how did you handle aggregation of all the test reports from each machine for test reporting?
9 days later
Firstly, I am suing different appium & wda port for each device (wda for iOS with XCUITest).
We are creating Master-slave pipelines for aggregation of the test reports from each machine (Jenkins)
@sanjit1walia can you please clarify if you're using TestNG / JUnit / Cucumber for paralleling tests ?
Any reference to blog or sample code can be useful. Thanks in advance.
@VikramVI Using cucumber for parallel tests.
Don't have a blog yet, will create sample code and push it in my public git repo
@sanjit1walia Thanks for reply, please ping back here; once your public repo is live 
10 days later
Hi @sugatmankar I am already configured all the things step by step but unable to launch parallel ios testing. Do you have any step by step document so that i can use as reference. Below are my Configuration.
Mac Version :- 10.12.2 MacOS Sierra
Appium :- 1.6.3
Xcode :- 8.2
iPhone6 :- 10.2.1
iPad2 :- 10.2.1
Eclipse Mars2.
Do we need to configure selenium stand alone server for parallel execution on the same machine or any other configuration needed ? If you have some document or steps of configuration it would be very helpful for me.
Thanks In Advance.