Keep what the test was meant to prove.
Inventory critical journeys, environments, credentials, schedules, and failure ownership. Recreate a small pilot suite in AuraCheck and compare the evidence your team needs for a release decision.
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
Confirm export and contractual options directly with your current provider.
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