---
title: "Test Versions & Steps"
id: "1926"
type: "page"
slug: "test-versions"
published_at: "2026-09-30T22:18:25+00:00"
modified_at: "2026-10-01T00:11:02+00:00"
url: "https://xedant.com/agents/test/docs/test-versions"
markdown_url: "https://xedant.com/agents/test/docs/test-versions.md"
excerpt: "Every change to a test is saved by itself. That is why you can always…"
---

# Test Versions & Steps

[https://xedant.com/agents/test/docs/test-versions.md](https://xedant.com/agents/test/docs/test-versions.md)

Every change to a test is saved by itself. That is why you can always look at what was there before, which version the test is written in today, and which version ran in a particular run.

This makes analysis noticeably easier: when a build went red, you see not only the difference in the picture but also whether the test itself had been changed right before that.

## Version history

On every write of a test, its content is saved as a separate version. The list shows where a version came from:

- **manual edit** — a person corrected the test;
- **AI fix** — a heal proposal a human approved;
- **AI improvement** — an improvement proposal, also approved by a human;
- **restore** — a return to an earlier version.

A run remembers which version it took. So a result is always tied to the exact edition of the test, not to “what the file later became”.

## The test page

The test page gathers everything about it: the title and tags, the steps, the recent builds, the version history, the discussions, and the export. There is also a scaffold for moving to Playwright — for the case when the tests move outside the product: nothing is lost, because the tests already live as plain files in the project.

Any earlier version can be brought back with one button. The file is written byte for byte, and the restore itself becomes a new version — history is never rewritten after the fact. Beside it, the total number of accumulated versions is visible.

There is one honest case: when a test file is deleted outside the product, the history does not disappear silently. It is marked orphaned — with the number of surviving versions — and can be viewed or cleaned up by a separate action.

## The step page

Every step has its own page, addressed by its ordinal number. It shows what the step does, which capture it declares — including the number of masks and whether it is a shared component — how its results looked in the recent runs, and which baselines it has.

A step can be disabled, with a reason named; beside it there is an optional review date — so the decision is not forgotten. A disabled step is simply skipped in future builds, while its baselines and key stay in place: it can be re-enabled at any moment without consequences. The reason, the date, and the cancellation itself all land in the audit log.

The circle is closed: how it all works as a whole and where to start — in [Visual Testing](/agents/test/docs/visual)
.

[← Back to the documentation index](/agents/test/docs)