[iOS9 UIAutomation] What is Appium approach to UIAutomation deprecation by Apple

Feature
51

Are you setting an implicit wait value? if so don’t do that for now, it causes a problem
What language are you using? if the c# driver then you wont be able to progress past loading the app as there is a probelm with the format of the json returned in the messages. see here: https://github.com/appium/appium-xcuitest-driver/issues/15

You could try using the 1.0.1 version of xcuitest and update the WebDriverAgent folder as a I mentioned previously.

52

I am using Java. It is actually crashing before I can ever get to the point where I would be able to set an implicit wait. Like I said in my last post, it crashes on the line:
driver = new IOSDriver(urlAddress, capabilities);

Since it crashes here, I am never able to create the driver to use it in any way.
This leads me to believe if it is an issue relating to my code, it must be a capability or url issue.

I have now tried with the xcuitest driver 1.0.1 using the webdriveragent you suggested from installing webdriver agent. This gave me an error similar to my very first post except it was “xcodebuild failed with code 70 instead of 65.” I also tried 1.0.1 xcuitest with the webdriveragent from 1.0.0 and got the same error from my last post:

info JSONWP Proxy Got response with status 200: {“value”:“Interrupting test”,“sessionId”:null,“status”:13}

It seems like there is something going on with the new webdriveragent, however, it also seems like there is something else going on here which is causing the crash.

@jonahss Do you have any ideas? I would really appreciate it, this is a major blocker on my current project.

1 Like
53

Can some one please help me in this regard?

Thanks for your time.

54

What about xciutest usage for now? Is xcuitest-driver ready? What status this thing has?

55

Hello, I want to test the appium-xcuitest-driver. I installed with npm install -g appium-xcuitest-driver. How do I run this now? Or how do I make sure that Appium is using this driver now, when I run my tests instead of the old ios-driver? Like forcing Appium to pick up that driver! When I let the new driver run with node it starts listening on localhost, but if I start my test now, we kill all drivers and start a new one. Now its not picking up the xcuitest-driver. When I set capabilities.setCapability(“automationName”, “xcuitest”); doesnt help either, it states: Details: The desiredCapabilities object was not valid for the following reason(s): automationName xcuitest not part of Appium,Selendroid,WebDriverAgent.
thanks for some help what the next steps could be to get it to run

1 Like
56

has anyone tried the appium-xcuitest-driver for tvOS? If so, can someone post a sample desired caps for that? I tried running one of my iOS tests with this driver, seems fine. However, I can’t seem to get it working on the Apple TV Simulator (tvOS 9.2, latest Xcode 7.3.1).

Also asked here: Apple tvOS Support

57

Hey, can you maybe ave a look at my question above and help me? I can not help you with tvOS, because I dont even get my iOS tests to pick up the xcuitest-driver and how I understood it, you did…yey. thanks for some info

58

@julesmummdry:
In my case, I started the new appium server (appium-xcuitest-driver) using “Node .”
My tests don’t kill and restart the appium server, so they just started using this new server. Now, I did not go deep and run all my tests, just checked a basic one where I can launch the simulator and login to my application.

The capabilities.setCapability(“automationName”, “xcuitest”) will not work now. This will work only when Appium bundles this driver into their future appium 1.5.x release (hopefully). For now, this driver is meant to be used on its own.

One way I see for you is to modify your test code to not kill and restart Appium server (easiest). There could be other ways like maybe uninstall Appium, and modify your automation to kill/start this other Node process instead.

1 Like
59

@jonahss
I have appium 1.5.3 installed on my MAC.Does XcuiTestDriver now a part of this Appium latest version?

Thanks and Regards,
Pranoday

60

Nope, we have not yet included XCUITestDriver into appium yet. You will see a note in the Appium Release notes when it is added.

61

Hello guys.
How to run XcuiTestDriver using node?

Regards,
Pranoday

62

According to the below Appium roadmap, version 1.6 with “XCUITest backend integration” has an ETD of 3/2016. Do we have a new ETD?

Roadmap: https://github.com/appium/appium/blob/master/ROADMAP.md

63

I think we do! Let me get a firm date on that.

iOS 10 removed Instruments and only supports XCUITest so we will make sure to have XCUITest working great before ios 10 is released.

Isaac just bundled the appium-xcuitest-driver into the main appium project in our master branch on github. We will be including beta support for XCUITest in appium version 1.6.0

After a beta period where people can help us find bugs, we will publish another version with better support.

We plan to publish all this before Apple’s official release of ios 10

3 Likes
64

Hello guys.
How to run XcuiTestDriver using node?

Regards,
Pranoday

65

@jonahss You mentioned under Advantages of the new XCUITest driver that “Is able to run on multiple connected devices in parallel”. I haven’t given it a try. But just curious. Does the same hold true for simulators also. Can i run multiple simulators in the same machine.

66

Hi @mathewkuruvila .
It should be true for Simulators as well.Instruments was not allowing running tests parallely on multiple devices/emulators attached to/started on single MAC machine.Now after introduction of XcuiTest there is no involvement of intruments.

Thanks and Regards,
Pranoday

67

wow that’s great. thank you

68

Hi @mathewkuruvila.
Can you please help me out in starting XcuiTest driver through Node?

Thanks and Regards,
Pranoday

69

Instruments is/was not the limiting factor. We used MonkeyTalk and (thanks to Oracle) are now using Appium, which both are utilizing Instruments to install and launch apps on real devices. Our Mac minis were handling 4 devices in parallel each without a problem.

It’s the simulator itself which cannot be started a second time on the same machine. There are guide to do this by starting the simulator with different Mac OS users, but we have not tried this yet.

70

Hi @Pranodayd,

Here is what I have tried… Discussion: Getting existing automation to run with new Appium XCUITest driver

We have decided to wait for the next Appium realease which is (hopefully) bundled with the XCUITest driver.