Skip to content
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

I'm trying to use this strategy and TC fails when cannot find first element. #920

Closed
livastar opened this issue Sep 5, 2017 · 5 comments

Comments

@livastar
Copy link

livastar commented Sep 5, 2017

@HowToUseLocators(androidAutomation = ALL_POSSIBLE)
@AndroidFindBy(id = "back_button")
@AndroidFindBy(uiAutomator = "new UiSelector().descriptionContains("Navigate up")")
public WebElementFacade backButton;

@livastar
Copy link
Author

livastar commented Sep 5, 2017

I've tried to separate find strategy into 2 elements, find by id and find by uiautomator.

The thing is that separate I can find the 2nd element, 'cause it is present on the screen.

This means that @howtouselocators strategy doesn't work as expected.

@wakaleo
Copy link
Member

wakaleo commented Sep 5, 2017

Your best best is to dig into the code and to see how Appium uses this annotation and where/how it is/should be being invoked by Serenity.

@livastar
Copy link
Author

livastar commented Sep 5, 2017

@TikhomirovSergey :) will appreciate your input :)

@wakaleo
Copy link
Member

wakaleo commented Sep 5, 2017

@TikhomirovSergey, @livastar, @vikramvi - if you let me know your email addresses, I will add you to the Serenity Developers slack channel, which might make coordinating the Appium integration work easier.

@livastar
Copy link
Author

livastar commented Sep 5, 2017

ivanostanis@gmail.com,
@pisarenco92 - pisarencogrigore@gmail.​com

Thanks a lot @wakaleo

@wakaleo wakaleo closed this as completed Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants