Disparity of Selector behavior between Android and iOS

[bartekpacia]

Patrol has the Selector and NativeView classes. They provide cross-platform interaction with the underlying native UI.

Currently, there are many differences Selector and NativeView between its behavior on Android and iOS.

More about these 2 classes

Selector

On Android, Selectors are translated to BySelectors and/or UiSelector.

On iOS, Selectors are translated to XCUIElementQuery-ies. Sometimes, we construct them using NSSelector. They allow for searching using many view properties: identifier, title, label, value, and placeholderValue.

NativeView

On Android, NativeViews are created from UiObject2s.

On iOS, NativeViews are created from XCUIElements.

Problems

• on iOS, only Selector.text is taken into account when searching for views
• some Selector fields, such as resourceId, are Android-only. That's because the Selector API predates iOS support.
• some NativeView fields, such as resourceName, are Android-only. Cause the same as above.
• Implementation of getNativeViews on iOS #1403
• Webview interaction - selecting correct element when Selector applies to multiple elements #663

[fylyppo]

On iOS Selector.className and Selector.instance are taken into account also.
It'll be good to have also textStartsWith and textContains on iOS.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue.