Which migration strategy best preserves Protractor-specific locators?

Transitioning from Protractor to Modern E2E Frameworks

Protractor provides specialized locators such as by.model(), by.binding(), and by.repeater() that hook directly into Angular's internal state. These finders simplify element selection by targeting the application's data-binding logic rather than relying solely on DOM attributes or CSS selectors.

As Protractor has reached end-of-life and the Angular team has deprecated the tool, teams must migrate to alternatives like Playwright, Cypress, or WebdriverIO. However, these successors do not natively support Angular-specific locators, necessitating a complete rewrite of the selection logic across the test suite.

When moving away from a legacy suite that relies heavily on these internal hooks, there is uncertainty regarding the most maintainable replacement strategy to avoid fragile CSS selectors.

• Does a standardized mapping exist to translate by.model or by.binding into stable data-attributes?
• Which successor framework offers the closest functional equivalent to Protractor's automatic synchronization with the Angular digest cycle?