Overview
Version history replays any saved version of a test inside the test editor. Spur marks what changed in that version and shows the runs that happened while it was live. Use it to find out when a step changed, who changed it, or to roll a test back to a version that was passing. Spur creates a version each time you save the test.Open version history
1
Open a test in the test editor
Open the test from your Test Suite.
2
Open the overflow menu
Click the three-dot menu in the editor’s top bar and select Version history.
3
Pick a version
Select a version in the version rail. The editor shows that version in read-only mode. Editing is disabled while you browse versions.
Read the changes
When you view a version, Spur compares it with the version before it.- Steps get an Added, Modified, or Deleted label. Modified steps highlight the words that changed.
- Settings cards that changed show a Modified badge. This covers Viewport, Cookies, Advanced configurations, and the test title and URL.
- Headers
- Route overrides
- HTTPS credentials
- Uploaded files
- Scenario links
- Ready/Draft status
The version rail
Each row in the version rail shows:- When the version was saved and who saved it. The newest row is labeled Current version.
- Whether the test was edited manually or with AI (Spur chat or MCP).
- A summary of the runs that happened while that version was live, such as passed, failed, or errored counts.
Spur matches runs to versions by save time, so the match is approximate. A run that started under one version may have finished after the next save. Spur marks those runs in the run history.
Name a version
Open a row’s options menu, select Name this version, type a name, and press Enter. Named versions are easier to find later, for example “Before checkout redesign.”Restore a version
1
Select the version to restore
In the version rail, open the version’s options menu and select Restore this version.
2
Confirm the restore
The confirmation dialog lists the untracked fields that keep their current values. If you have unsaved edits, restoring replaces them.
3
Review and save
Spur loads the version into the editor as unsaved changes. Review the test, then click Save to keep it.
