[SOLVED] Native XCUITest selection strategy

Emil_Petersen 2017-01-04 16:58:14 UTC #1

Hi all,

Is there any word of a native XCUITest selector strategy, to replace the not-intended-for-XCUITest XPath strategy, and the now-obsolete ios_uiautomation (python naming) strategy?

If not I would be interested in working towards contributing this new selector strategy as it would be very useful to me, and hopefully to other people.

I did not find it being discussed on github yet.

If there is currently nobody working on it, could anyone here point me towards some resources on how to go about implementing it? Is there anyone else with experience who would be willing to help towards this goal?

Kind Regards,
Emil R. Petersen

richard.li 2017-01-04 19:27:38 UTC #2

Me too. I did lot's of research and got few docs regarding Nspredicate for Appium. eg. https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/ios_predicate.md only one example for nspredicate. How can I locate cells or statictexts on the iOS app? How can I get particular elements using nspredicate?

Thank you very much in advance.

Emil_Petersen 2017-01-05 14:40:14 UTC #3

Hey Richard, thanks for making me aware of the iOS predicates. It seems that while tests were added for the python-appium driver, the documentation was not updated.

I don't know if you're using Python, but either way, have you tried a strategy like this? https://github.com/appium/python-client/blob/master/test/functional/ios/find_by_ios_predicate_tests.py

I'm thinking particularly the last example there, which may (I have yet to test this selection strategy) allow you to select by type and then the value of certain fields.

Take my advice with a grain of salt since your comment taught me this exists, and I haven't tried it yet. Good luck.

Emil_Petersen 2017-01-05 16:23:49 UTC #4

Turns out that the python-driver documentation was not updated, and that this has been added since the move to XCUITest!

Using (python syntax) find_element(s)byios_predicate works perfectly, and is a great replacement for UIAutomation and XPath on XCUITest-supported devices. I have now tested it myself and been very happy with the results.

Cheers to the Appium team for their timely and awesome adding of support of XCUITest!

ailyenko 2017-01-09 19:22:38 UTC #5

How can it be used in findBy annotations (java)? Should we use @iOSFindBy(uiAutomator = "isWDVisible == 1") ?

richard.li 2017-01-10 14:38:14 UTC #6

You could try these links:
XCUITModeTest demo code:

github.com

appium/java-client/blob/master/src/test/java/io/appium/java_client/pagefactory_tests/XCUITModeTest.java

/*
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * See the NOTICE file distributed with this work for additional
 * information regarding copyright ownership.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */


package io.appium.java_client.pagefactory_tests;

import static io.appium.java_client.pagefactory.LocatorGroupStrategy.ALL_POSSIBLE;

This file has been truncated. show original

Java-client 5.0BETA1 Page-objects documentation:

github.com

appium/java-client/blob/master/docs/Page-objects.md#--chained

Appium Java client has facilities which components to [Page Object](https://github.com/SeleniumHQ/selenium/wiki/PageObjects) design pattern and [Selenium PageFactory](https://github.com/SeleniumHQ/selenium/wiki/PageFactory).


# WebElement/list of WebElement field can be populated by default:
```java
import org.openqa.selenium.WebElement;
import org.openqa.selenium.support.FindBy;
...

@FindBy(someStrategy) //for browser or web view html UI 
//also for mobile native applications when other locator strategies are not defined
WebElement someElement;

@FindBy(someStrategy) //for browser or web view html UI 
//also for mobile native applications when other locator strategies are not defined
List<WebElement> someElements;
```

# If there is need to use convinient locators for mobile native applications then the following is available:

This file has been truncated. show original

I am trying to implement these to my legacy code which using iOS predicate but not iOS predicate String. There are lots of headaches. Furthermore, I am not sure how to locate multiple layers elements same like iOS predicate ".tableViews()[0].cells()[1].....".

Gook luck!