Auto-Recovery

Auto-recovery is Checksum’s real-time test maintenance system. When a test step fails during execution, the CLI’s AI fallback immediately attempts to recover — finding the right element, adjusting timing, or adapting to UI changes on the fly.

How It Works

1. A test runs and a step fails (e.g., a button can’t be found)
2. The CLI’s AI analyzes the current page state — what’s visible, what changed
3. It attempts to recover: finding the element by alternative means, waiting for the right condition, or adapting to the new UI
4. If recovery succeeds, the test continues and the step is marked as healed
5. If recovery fails, the test is marked as failed and escalated to auto-healing

This all happens transparently during test execution — no manual intervention needed.

---

What Auto-Recovery Can Fix

Issue	How It Recovers
Changed selectors	Finds the element using alternative attributes (text, role, position)
Timing issues	Waits for the right conditions before proceeding
Minor UI changes	Adapts to layout or text changes that don’t affect the flow

---

What Auto-Recovery Can’t Fix (But Auto Healing can!)

Some issues require deeper analysis and code changes:

• Major flow changes (steps added or removed)
• Completely redesigned pages
• Changed business logic
• New authentication requirements

These are handled by Auto-Healing, which creates a full AI agent session to fix the tests.

---

Viewing Recovery Results

In your test run results, recovered tests show up in the healed count:

Result	Meaning
Passed	Test passed without any recovery needed
Healed	Test had a failure that was automatically recovered
Failed	Test failed and couldn’t be recovered

---

Enabling Auto-Recovery

Auto-recovery is enabled when the test run is configured in auto-heal mode. The run mode is configured in your project settings — when enabled, failing test steps will automatically attempt recovery before being reported as failures.