Find list of elements with multiple locator strategies

MajDroid 2017-11-08 13:02:35 UTC #1

Using Page Object Pattern and its annotations to find a particular element, however this element has different possibilities, I tried to use all the locator strategies explained in this page:

github.com

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

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

The problem with (ALL_POSSIBLE) strategy is that it will get all the result of all strategies that apply, for example:
@HowToUseLocators(androidAutomation = LocatorGroupStrategy.ALL_POSSIBLE)
@AndroidFindBy(xpath = “strategy1”, priority=0)
@AndroidFindBy(xpath = “strategy2”, priority=1)
@AndroidFindBy(xpath = “strategy3”, priority=2)
@AndroidFindBy(xpath = “strategy4”, priority=3)
List elements;

It might return a list of elements that apply for 2 of the above strategies while i presumed that it will only return the result of the first successful strategy according to the defined priority.

Is there a workaround for this?

Thanks in advance.

MajDroid 2017-11-15 10:39:19 UTC #2

After looking into the source of the Java client, I think it will apply the first one if was fetching for a particular MobileElement but in my case, I’m fetching a list of MobileElements which results in applying all BYs and getting their results instead of getting the first successful match.