Keep what the test was meant to prove.
Pick a small set of critical journeys and agree on acceptance criteria for coverage, setup effort, and failure diagnosis. Run a AuraCheck pilot before changing the existing release gate.
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
Use a side-by-side evaluation rather than assuming feature or pricing parity.
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