Keep what the test was meant to prove.
Extract the user journey from your Cypress spec, including setup, authenticated state, and expected UI changes. Rewrite it as small, explicit actions and assertions for review in AuraCheck.
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
Do not assume custom Cypress commands or network intercepts transfer automatically.
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