Keep what the test was meant to prove.
List the business intent behind your locators and assertions. Preserve stable unit and API checks in Playwright; evaluate AuraCheck on the UI journey where selector maintenance consumes time.
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.
Before you switch
Keep your existing suite running while comparing failures on the same build.
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.
Prepare your first AuraCheck project