UI Automation, reusing code within a different framework, or hacking how it works?
I have a lot of JavaScript code for UI automation that is no longer in use since support has been removed in Xcode.
I am looking for any ways to try reusing as much code as possible.
I was just wondering if there is some migration or hack path to make it usable? I haven't seen anything yet.
source to share
Okay, I've waited long enough for iOS QA Automation Engineers to share their professional take on this question, but since no one showed up, I'll give it back.
First, you are not alone. UI Automation support has been removed since XCode 8 and many others have had the same issue .
The main takeaway from all the materials I read on the Internet is this:
The only Appium version that will work with xcode 8 is 1.6.0. You can now download the beta. Tools / UIAutomation has been removed and Appium XCUITest support will work forward.
Moving ahead, the best document to get started with test case migration, or at least give you some support tips: Migrate your iOS tests from UIAutomation (iOS 9.3 and below) to XCUITest (iOS 9.3 and above) . [UPDATED LINK].
The article covers some pretty hot topics that address your situation:
- Element class name schema;
- Page source;
- Locator strategies (with emphasis
xpath
); - Dependencies, API differences, etc.
You will need to start using appium-xcuitest-driver instead of appium-ios-driver .
Installation and configuration:
Besides the relevant information you will find on the appium-xcuitest-driver official GitHub repository , the bread and butter is here: Configuring iOS Real Devices Tests with XCUITest .
Getting started with a new base / set of libs or porting from one toolbox to another is always tricky, but from past experience, once you have a working setup and create your first test case, everything else should go smoothly after that.
Finally, I could extend the answer, but the official documentation
source to share