Make UI automation friendly?

[fmorency]

Not sure if this is a real issue as I am a complete web UI newbie, but it seems that some UI ids, e.g., id=tabs-21--tab-1, change from tab to tab.

I am using UI.Vision RPA to generate screenshots for the onboarding documentation, and the tool needs a non-changing name/id otherwise, the macro cannot replay correctly.

Is assigning a non-changing name/id to all UI components possible?

Also affects Alberto.

[stanleyjones]

I'll look into UI.Vision RPA but in Alberto we use ARIA roles, as recommended here: https://testing-library.com/docs/queries/about#priority

Based on the Guiding Principles, your test should resemble how users interact with your code (component, page, etc.) as much as possible. With this in mind, we recommend this order of priority:

1. Queries Accessible to Everyone: Queries that reflect the experience of visual/mouse users as well as those that use assistive technology.
2. Semantic Queries: HTML5 and ARIA compliant selectors. Note that the user experience of interacting with these attributes varies greatly across browsers and assistive technology.
3. Test IDs

[fmorency]

I used UI.Vision RPA for some documentation because I needed screenshots. However, components were not easily accessible by id/name.

Not sure what the right FE way of doing this but I'm open to discussion.