> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testsprite.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Rerun
> Re-execute a single UI test, the whole project, or a scheduled run — from the dashboard, in a batch, or on a cadence.
## What Rerun Does
Rerun re-executes a UI test against your live app using the test's saved Playwright script. Same actions, same assertions — replayed from scratch. There are three places you can trigger a rerun from, plus an optional **Auto-Heal** toggle that recovers tests when the page changed but the flow is fine (Pro plans).
This page is about plain rerun — what it does, where it lives, and how to use it. The Auto-Heal mechanics live on their own page.
How TestSprite recovers UI tests when the page changed but the flow is fine
## Quick Start
From your project's **Integration Tests** list (sidebar default for UI projects), click into the test.
The button in the right panel's tab bar is labeled Run when the editor is clean, or Save & Run when there are unsaved edits. Clicking it opens the **Rerun this test** confirmation dialog.
The dialog has one toggle: **Auto-heal on UI drift** (Pro). Free-plan users see it locked with a Pro badge; Pro-plan users can toggle per rerun.
Replay starts immediately. If you opted into Auto-Heal and the page has changed, the test is recovered automatically — see [Auto-Heal](/web-portal/core/ui/auto-heal) for what it covers.
The test detail page updates in real time. You can stay and watch or navigate away and check the result later.
## Three Rerun Surfaces
### Single Test Rerun
From a test's detail page, click Run (or Save & Run if there are unsaved edits) → confirm in the **Rerun this test** dialog → done. The Auto-Heal toggle in the dialog is decided per rerun.
### Rerun All (Batch)
The Rerun all button on the project's Tests page toolbar queues every test in the project — useful after a refactor, dependency upgrade, or design pass. The Auto-Heal opt-in applies to the whole batch; tests that pass cleanly cost the same as a regular rerun, so opting in doesn't penalize a healthy suite.
### Scheduled Reruns
Schedules re-run your tests on a cadence (Hourly, Daily, Weekly, Monthly) and carry their own **Enable auto-heal** toggle, set once at creation. Agent minutes are only consumed when replay actually fails, so a schedule full of clean tests stays cheap — and overnight UI drift gets absorbed instead of paging someone in the morning.
Set up cadences and route notifications
## Edge Cases & Troubleshooting
Rerun replays the *saved* script. If you regenerated the test through Refining or a fresh generation, the saved script may be stale relative to your latest plan. Try a regular Run (not Rerun) to overwrite the saved artifact, then Rerun.
The test detail page subscribes to live status updates. If you don't see progress within a few seconds, refresh — the rerun is still happening server-side; this is just a live-update hiccup.
The single-button design means clicking Save & Run always saves first. To rerun without saving, discard your edits via `Cmd`/`Ctrl`+`Z` or by reverting the editor, then click Run. There is no "rerun-without-save-from-dirty-state" path by design — the dirty indicator (warning dot) signals you'd be running a different script than what's persisted.
Either the project has no tests yet (still in plan-gen), or another project-level operation is in flight (e.g. an active wizard run). Wait for that to complete; the button re-enables when the project is idle.
## Where to Go Next
Recover UI tests when the page changed but the flow is fine
See exactly what happened on each step of a run
Set up nightly schedules to catch drift early
Diff two runs to see what changed step-by-step