-
Notifications
You must be signed in to change notification settings - Fork 564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$$ and $$x are missing for Appium selectors #2333
Comments
@kamil1014 - For now, you can still use Selenide.$$(by) I will create a PR to have it in SelenideAppium class as well |
@asolntsev we may also want to include public SelenideAppiumElement $(WebElement element){
//logic to return SelenideAppiumElement;
} Also when using pagefactory, we should provide an option to use SelenideAppiumElement reference @AndroidFindBy(xpath = "//android.view.ViewGroup[@content-desc=\"store item\"]")
@iOSXCUITFindBy(xpath = "//*[@name='store item text']")
private SelenideAppiumElement products; |
Thanks, came a cross the same issue. |
It already works. You can declare PO fields (annotated by |
@kamil1014 @amuthansakthivel The point of collection is to check texts/attributes of multiple elements with a single call. And it's totally possible with the current |
this commit introduces new type SelenideAppiumCollection which is a collection of SelenideAppiumElement's (like ElementsCollection is a collection of SelenideElement's).
this commit introduces new type SelenideAppiumCollection which is a collection of SelenideAppiumElement's (like ElementsCollection is a collection of SelenideElement's).
The problem
There are missing $$ and $$x operators for finding Appium collections of elements.
There are only $ and $x operators in SelenideAppium class.
Details
If there is other way to get collection of appium elements using Selenide please let me know.
Tell us about your environment
Code To Reproduce Issue
The text was updated successfully, but these errors were encountered: