Auto-Maintenance

Checksum solves this with two complementary systems that keep your test suite green automatically:

Auto-Recovery — Real-time fix attempts during test execution
Auto-Healing — Batch repair of failing tests after CI runs, delivered as PRs

Together, they create a zero-maintenance testing experience.

Why Tests Break

Common reasons tests fail after app changes:

Cause	Example
Selector drift	A button’s `data-testid` or text changed
Timing issues	A page loads slower after a new feature was added
Assertion mismatches	The expected text or value changed
Flow changes	A step was added or removed from a user flow
Setup drift	Test data requirements changed

Checksum handles all of these automatically.

The Two Layers

Layer 1: Auto-Recovery (During Execution)

When a test step fails during execution, the CLI’s AI fallback kicks in immediately and attempts to recover on the fly. This happens transparently — if recovery succeeds, the test passes and the healed count increments. → Learn more about Auto-Recovery

Layer 2: Auto-Healing (After CI Runs)

When tests fail in CI and can’t be auto-recovered, Checksum creates a healing session — an AI agent that analyzes the failures, fixes the test code, and opens a PR with the fixes. This supports both Standard and Deep modes. → Learn more about Auto-Healing

The Maintenance Loop

Tests run in CI
  → Some tests fail
    → Auto-recovery fixes them in real time (if possible)
    → Remaining failures trigger auto-healing
      → AI agent fixes the tests
      → PR opened with healed tests
        → You review and merge
          → Tests are green again

Getting Started

Test Creation

CLI & CI

Maintenance & Monitoring

Integrations

Security & SSO

Why Tests Break

The Two Layers

Layer 1: Auto-Recovery (During Execution)

Layer 2: Auto-Healing (After CI Runs)

The Maintenance Loop

Next Steps

​Why Tests Break

​The Two Layers

​Layer 1: Auto-Recovery (During Execution)

​Layer 2: Auto-Healing (After CI Runs)

​The Maintenance Loop

​Next Steps

Why Tests Break

The Two Layers

Layer 1: Auto-Recovery (During Execution)

Layer 2: Auto-Healing (After CI Runs)

The Maintenance Loop

Next Steps