Android xpath - sustainability?

I am testing a Xamarin app for Android. It is a big change from Web apps.
There are no ID tags. Most of the elements do not have text attributes/labels.
My question is - do people really have success with xpath or is there something I should speak to a developer to improve support for automation? Can I simplify the mess below and make it a relative xpath?
A typical xpath looks like this:

Thanks for any support, Dan

You may find the following article interesting.

You should interpret “Ext JS” --> “Mobile App” and “Selenium” --> “Appium”. At one layer of abstraction up, the article applies to your case as well.

I suppose you should discuss with your developers to tune your AUT with E2E testing in mind.

1 Like

Hi - thanks, that’s a useful read and I think my options are:
a) handcraft xpath for objects that lack unique identifier, since Object Spy/Recorder for Mobile only offers absolute xpath (and does not appear to work for mobile tests)
b) ask Dev to add some identifiers

For option a), I note that we can’t verify mobile xpath in Object Spy, like you can for web apps (for example, I try ‘//*[@text=‘Incident No.’]/following::android.widget.EditText’). Tester must execute test to verify if this locator is correct. This seems like a useful feature request, unless I’m missing something.
Regards, Dan