So on iOS it’s a little different, right? Doesn’t Appium set UIAApplication
to be root by default and then xpath calls like /UIAWindow[1]
work?
I don’t know what the correct design call is, but I think the internals of Appium, how it deals with invalid xml, should be hidden and an effort made to standardize crossplatform.
I don’t want to write /hierarchy/android.widget.FrameLayout
’ when I want root. I want to write /android.widget.FrameLayout
.
Then, if/when UiAutomator is updated, and it actually returns valid xml, Appium can remove the /hierarchy
workaround, and my client doesn’t need to care.
shadow element?