-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
UiSelector being deprecated #812
Comments
Right now it is probably too early to discuss the deprecation topic, although it definitely makes sense to add the above link to the driver documentation now. Eventually we will have no choice in following Google when they decide to kill UiObject completely. |
Yeah, good point. Maybe we can create a BySelector parser as we did for UiObject? |
I have some tests which use |
Hi,
I wanted to bring this into your attention that UiSelector is being deprecated in future releases for Android UiAutomator2.
Please see https://developer.android.com/training/testing/other-components/ui-automator
If this is true, does that mean any locators using UiSelector will not work in future?
If yes, then would be good to also mark it deprecated soon in Appium so users can adapt their code bases accordingly with alternate locator strategies. Moreover to mark this upcoming deprecation here in docs as well and provide some alternate examples:-
https://github.com/appium/appium-uiautomator2-driver/blob/master/docs/uiautomator-uiselector.md
Moving forward, what would be the recommendation from Appium team to build android locators? Does Appium support building locators via other APIs such as with BySelector?
See also #13670
The text was updated successfully, but these errors were encountered: