Retire one brittle locator at a time.

Keep what the test was meant to prove.

Choose a representative WebDriver flow. Document the browser state, business assertions, and test data before rebuilding the journey with AuraCheck’s visual approach.

Use the same build and expected outcome.

Document prerequisites, test data, and the final assertion. Recreate the case in AuraCheck, review the generated automation, and run against a controlled environment. Compare the evidence and the effort required to understand a failure.

Move ownership, not just execution.

Agree who reviews the case, maintains the environment, and triages failures. Keep the old release gate until the pilot has demonstrated repeatable outcomes. Expand one feature at a time, retaining existing unit and API coverage.