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.
What Step-by-Step Shows
The Steps panel sits inside the test detail page’s Overview tab — one row per action and assertion the test took during execution. A Test Result block at the top shows the run-level outcome (PASSED / FAILED / BLOCKED / RUNNING); click any step row to load the HTML snapshot of the page at that moment in the right pane.
| Element | What it shows |
|---|---|
| Step number | Order in the run (1, 2, 3…) |
| Action / Assertion | The kind of step — click, fill, navigate, scroll, wait for actions; visible, text, url, enabled for assertions |
| Description | Plain-English summary of what the step did or checked |
| Status | Green (passed), red (failed), neutral (no assertion) |
Where to Find It
Click any UI test from the project test list to land on its detail page (see Test Detail for the broader page). The Steps section inside the Overview tab is the Step-by-Step view.
Step data persists with the test row, not with the run. The Steps section always shows the steps of the most recent run for that test. Older run history requires comparing two runs (see Comparing Runs).
The Video and the Snapshot
The test detail’s right pane has a Preview tab with the full recorded video (default browser controls — play/pause, scrubbing, speed, mute) and a Code tab with the test code. When you click a step in the left-side Steps list, the right pane swaps to an HTML snapshot of the page at that step. Click the Test Result block at the top of the steps list to return to the video view.
Failure Localization
The failed step row is highlighted in the list. Click it to load the HTML snapshot from that moment, then open the failure detail panel below for the diagnosis.
| Tab | What you see |
|---|---|
| Error | The headline failure message — with a friendly explanation prepended for common error families TestSprite recognizes (see below) |
| Trace | The raw stack / step trace from the run |
| Fix | An AI-authored cause-and-fix suggestion |
Recognized error families
TestSprite recognizes common failure patterns and prepends a plain-English headline:| Pattern | Headline shown |
|---|---|
| UI drift | ”There was an element UI drift which may have caused the issue. The page’s layout has likely changed since this step was recorded, so the expected element couldn’t be found in time.” — try Auto-Heal or refine the test description. |
| Auth failure | ”We encountered an issue logging into your site with the provided username and password. Please double-check your credentials and try again.” |
When the Steps Look Fine but the Test Failed
Sometimes every step shows Passed but the overall test is Failed. This is rare; typically caused by:| Cause | What it looks like |
|---|---|
| Final assertion outside the step list | Some test code asserts after the main flow finishes — the failing assertion isn’t tied to a step row |
| Hidden timeout | The run took too long overall, even though no individual step did |
| Post-run validation | A check that runs after the main flow detects something the in-flight asserts missed |
Auto-Heal and the Steps View
Auto-Heal reruns may follow a different action sequence than the recorded script. The steps list always reflects the most recent run, so an auto-heal rerun replaces it — but the saved test code stays untouched unless you explicitly save updates.Auto-Heal (Pro)
How Auto-Heal recovers UI tests when the page changed but the flow is fine
Edge Cases & Troubleshooting
The Steps section is empty for a test that ran
The Steps section is empty for a test that ran
The Steps panel shows “Collecting steps…” while the run is in progress and “No steps recorded for this test run.” if the run finished without producing step records. Refresh once the test status flips to Passed/Failed.
A step's HTML snapshot shows a blank page or a loading spinner
A step's HTML snapshot shows a blank page or a loading spinner
The action triggered a navigation/render but the snapshot was captured before the new state stabilized. Common with very fast pages or animation-heavy UIs. The next step’s snapshot usually shows the settled state.
The video is missing but the steps are there
The video is missing but the steps are there
Recording failed for this run. The steps + HTML snapshots still convey what happened; only the playback experience is degraded.
The steps show actions I didn't write into the test
The steps show actions I didn't write into the test
Auto-heal ran and recovered. The step list reflects what actually executed, not the original saved script.
Where to Go Next
Test Detail
The full test page with error trace, refinement, and rerun
Comparing Runs
Side-by-side step-by-step diffs between runs
Auto-Heal (Pro)
Re-execute with UI-drift recovery
Refining Tests
Adjust a step or whole test in natural language