Hi @jonahss: 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 appium-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. I read that its actually not needed to set capabilities. Do I have to delete or uninstall the appium-ios-driver?
thanks for some help what the next steps could be to get it to run with the appium-xcuitest-driver
Juliane
UPDATE PROGRESS:
I just deleted the appium-ios-driver from my node-modules and added the appium-xcuitest-driver. When I run my test now, it complaints that it cannot find module āappium-ios-driverā. How do I get Appium to use the new driver?
Hi Christian @Jander , I tried several things and replaced the index.js from the ios-driver with the new xcuitest-driver (like copied into the other), so the implementation of xcui is in the ios-driver so it doesnt complain about, that the it cant find xcui-test. But the interface is still quite different, thats why it doesnt run. I think for now we can just wait until they release it with Appium 1.6. and then it should be easy to use. Sorry that I couldnt help more. Cheers Jules
In the meantime, I have tried the following (without success):
Installed Node.js and NPM
Installed āappium-xcuitest-driverā
Changed the implementation in Appium.app/Contents/Resources/node_modules/appium/build/lib/appium.js to use the WebDriverAgentDriver (which is the one defined in appium-xcuitest-driver 1.0.4) if the platform is āiosā.
The current implementation of determineDevice() in driver.js does not yet support real devices (only simulator)ā¦ so I changed this implementation to return my real device without a check.
Next I ran into an error, that says, that the Info.plist could not be extracted from the ipa. But the same ipa works with the appium-ios-driver.
But unfortunately I cannot try it with the .app file or provide any further details (e.g. log outputs) before next week, because right now I have no access to the machine that we were testing on.
Oh yes there is much success. Weāre still working on getting it all ship-shape to work easily with no modifications. If you look at the repo, youāll see that @isaac has been very busy with it lately. Seems like weāre on track to have it published way ahead of the ios 10 release.
I just want to ask if there any news regarding āGetting existing automation to run with new appium-xcuitest-driverā. I also want to try the new webdriver for our regression executions. Unfortunately, I am still not able to run a existing automation run with appium-xcuitest-driver.
Are you able to give me an update, or a short how to?
see https://github.com/appium/java-client/pull/460 which states that āThe new AutomationName was added. IOS_XCUI_TEST. It is needed for the further development.ā so at least some preparation have been done already.
Hi Jander, do you have any specific steps you can share regarding what you followed please? ā¦ Attempting to see what I can get working but a bit unsure on step 3.
what I did in step 3 was just a quick hack in order to get it running.
I changed the appium.js file inside the Appium package (in the build subfolder) and simply returned the WebDriverAgentDriver instead of the IosDriver. I have added a new variable in analogy to the IosDriver (around line 40)ā¦
var _appiumXCUITestDriver = require('appium-xcuitest-driver');
ā¦ and returned it, if the platform name ist āiosā (around line 105).