Tricentis Tosca Automation Specialist Level 1 (AS1) Practice Test

When a UI element can change its attributes from run to run, build the locator from a mix of stable attributes and add fallback criteria so the element can still be found even if one attribute changes. Relying on a single fixed attribute is brittle because dynamic UIs often regenerate IDs, shuffle classes, or alter text. Text-only matching is also risky for the same reason—text can vary with localization or content updates. Avoiding element identification isn’t a viable strategy.

The best approach is to use flexible, multiple attributes with fallback criteria. Define a locator that requires several attributes together (for example, a stable tag, a portion of the class, a nearby label or aria-label, and a partial text match). Then provide alternative attribute sets or relational hints (like the element’s position relative to a nearby label) to try if the primary set fails. In Tosca, this means configuring the locator to combine attributes with AND logic and layering in fallback criteria that can be attempted if the first attempt doesn’t locate the element. This makes your element identification resilient to UI changes and keeps tests reliable.