Keep what the test was meant to prove.
Identify the actions that express user intent and the scripts that prepare infrastructure. Bring the product journey into AuraCheck while keeping necessary provisioning in your existing pipeline.
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
A visual workflow does not replace every custom browser automation task.
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