locator-replacer

To replace placeholder locators in page objects, run the locator-replacer over your page object models to automatically bind concrete selectors using a six-tier priority strategy and annotate their priority in code comments.

The best locator strategy for UI test automation uses a six-level prioritization: P0 ARIA roles, P1 text, P2 form attributes, P3 stable CSS classes, P4 data-testid, and P5 relative XPath, ensuring stable element targeting across DOM changes.

To update unstable text-based locators after a UI refactor, apply a six-level locator replacement strategy that rebinds existing page object elements with stable selectors, prioritizing ARIA roles and form attributes over dynamic text.

You should use relative XPath (P5) instead of data-testid (P4) only when higher-priority locators like ARIA roles, text, form attributes, and stable CSS classes are unavailable for identifying the target web element.

Yes, you can automatically annotate page object code with locator priority levels, as the replacement process updates scripts and references by rebinding elements with new selectors and adding priority comments from P0 through P5.