plu / pxctest

Execute tests in parallel on multiple iOS Simulators
MIT License
800 stars 57 forks source link

Run different tests on different simulators in parallel #19

Open nabsofken opened 7 years ago

nabsofken commented 7 years ago

So I can run the same tests in parallel in different simulators but is it possible to run different tests at the same time?

plu commented 7 years ago

Do you mean splitting a test target of 100 tests into two parts and then run them at the same time in two different Simulators?

nabsofken commented 7 years ago

yes

plu commented 7 years ago

You can try the --partitions 2 option, but it's still experimental! You also need to install the current master.

nabsofken commented 7 years ago

oh cool thanks I will try that

amesandy-zz commented 7 years ago

did that work for you?

JuliaGrasevych commented 7 years ago

As I understand, --partitions 2 will run separate test targets in parallel. What about splitting 1 target into couple parts and run these in parallel?

P.S.: When I use xctest run-tests --destination 'name=iPhone 6,os=iOS 10.2' --destination 'name=iPhone 5s,os=iOS 10.2' --testrun build/Products/TestUI_iphonesimulator10.2-x86_64.xctestrun --partitions 2 it gives me an error: nilError I have 2 UI test targets in project.

RichardGuion commented 7 years ago

I have the same error as Julia.

maryamaffinityclick commented 6 years ago

I am looking for the same scenario, running different test classes on different simulators. I think we can do it by

[-only-testing:] [-skip-testing:]

I didn't try yet, but I will update if I succeed on that :) and let me know if anyone has done that before.

benmarten commented 6 years ago

Did anyone get it working in this fashion? Sharding multiple tests from same target/scheme to multiple emulators?

maryamaffinityclick commented 6 years ago

@benmarten Yeah I achieved something you can read what I have done -> https://medium.com/@Maryamfekri/how-to-run-uitest-for-messaging-features-in-an-ios-application-777de0440b99 with passing some environment variable and running two test cases in parallel with only-testing !