refactor: loading xcuitest related methods only for XCUITest case

[KazuCocoa]

Eliminate global driver to enable multi-device automation within a single process #312

• run tests for iOS

[saikrishna321]

Is this possible with latest server ? Single server session which can handle multiple driver instances ??

[KazuCocoa]

If we use instance @driver, not a global driver, we perhaps can conduct multiple instances for iOS. Though, I'm trying to check the behaviour with test scenarios before next release.

[saikrishna321]

@KazuCocoa will wait to hear from you on this

[KazuCocoa]

@saikrishna321

Sorry for miss the comment. 😞

If we don't use the global driver, means we don't use promote_appium_methods and promote_singleton_appium_methods, I think we can handle multiple driver instances with current master ruby_lib.
And I'm working to reduce or remove the global driver more on this issue and plan to prepare test cases running on multiple instances by Xcode 11.

[saikrishna321]

@KazuCocoa

I think we can handle multiple driver instances with current master ruby_lib

Agree this is possible, but is this possible to with Single appium server session ?

[KazuCocoa]

Sorry, I'm a bit confusing 🙇
Which is the single appium server, the following's 1 or 2?

@driver 1(thread 1) ---session1---- single appium server----devices
@driver 2(thread 2) ----session2----/

@driver 1(thread 1) ----session1--- single appium server----devices
                  \-------session2------/

I guess 1 is possible but 2 is not.
But I'm not sure 1 is possible completely because I haven't implemented such case.

And

prepare test cases running on multiple instances by Xcode 11

I commented means I'll try to implement a test case like https://github.com/appium/appium-xcuitest-driver/blob/master/test/functional/parallel/parallel-simulators-e2e-specs.js