-
-
Notifications
You must be signed in to change notification settings - Fork 762
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
Feature: To support mix of search strategy #565
Comments
@amedvedjev It seems it is not the problem of java_client by itself. But it is possible that it is related to What will happen if you change annotation sequence like @HowToUseLocators(androidAutomation = ALL_POSSIBLE)
@AndroidFindBy(className = "android.widget.ImageView")
@AndroidFindBy(className = "android.widget.ImageButton")
@AndroidFindBy(id = "action_bar") It seems that ByAll returns the element tha was found first. By annotation sequence you can regulate the priority of the searching at ALL_POSSIBLE case. I'm not sure that it is needed to define the priority by annotations. However C# clint (Selenium and Appium too) page object attributes (annotations) can regulate it clearly. We could think about this feature further. |
what i need is:
e.g.
another possibilities are also welcome:
|
Ok. I will think about the design. It would be the interesting feature |
Thanks Sergey! also don't forget about CHAIN possibility. |
The fix was merged at #646. It is going to be available soon. |
Description
it does work now for "ImageView" correctly but for "ImageButton" not! For "ImageButton" it get "action_bar" instead.
The text was updated successfully, but these errors were encountered: