Manage manual test case versions
Katalon True Platform keeps a version history for every manual test case. Each saved change creates a new, immutable version — nothing is overwritten. Drafts and published versions are numbered separately, and every test run permanently records the exact version it executed, so past results never change when the test case is edited later.
Use cases​
- Review a teammate's edits: See every saved change to a test case — who made it, when, and with what status — before you publish it for the team.
- Keep execution evidence stable: A run always shows the exact version it executed. Editing the test case afterward does not change what a past run reports, which keeps audit and compliance evidence intact.
- Separate work in progress from the approved test: Keep editing as a draft while the rest of the team keeps running the latest published version.
- Re-run the same version for re-validation: Pick a specific version at run creation to repeat a past run against identical steps.
How version numbers work​
A test case version is either a draft or a published version:
| Type | Numbering | Status badge | Meaning |
|---|---|---|---|
| Draft (minor) | v1.1, v1.2, v2.1, … | Draft | Work in progress. Created automatically each time you save a change. |
| Published (major) | v1, v2, v3, … | Published | A version you promoted as ready for the team. |
- Every saved change creates a new version. Existing versions are immutable — they are never edited in place.
- Saving a change on a published version creates the next draft minor and switches the test case status back to Draft. For example, editing
v2createsv2.1 (Draft). - Publishing promotes the test case to the next major version. For example, publishing after
v2.3createsv3 (Published). - Test steps are committed when you click Save. Each save creates a new draft minor version.
- Other fields — priority, description, precondition, and metadata — save automatically. Each automatic save also creates a draft minor version.
Updating metadata or other non-step fields never creates a published major version. It increments the minor number and sets the status to Draft.
Publish a version​
- Open the test case in Test Case Details.
- In the status control, change the status to Published.
The test case is promoted to the next major version (for example, v2.3 becomes v3) and shows the green Published badge. Changing the status to anything other than Published keeps the test case as a draft minor version.
View a previous version​
Open the test case's Change History to see all versions. Each entry shows the version number, status, author, and timestamp, with the field values as they were in that version.
When you open a version that is not the latest:
- The version label shows which version you are viewing, for example
v1.2. - A Read-only indicator appears next to the version label. Only the latest version can be edited.
- Hover over Read-only to see the reason, for example: You are viewing v1 (read-only). Only the latest version (v2) can be edited.
Choose which version to run​
When you create a test run, each selected test case has a version selector in the Select Tests dialog:
| Option | What runs |
|---|---|
| Latest (default) | The newest version, whether it is a draft or published. |
| Latest Published | The newest published major version. |
| A specific version | Exactly that version — published majors and draft minors are both available, for example v1 or v1.1. |
Any version can be executed, including draft minors. This lets you trial-run a draft before publishing it, or repeat a past run against a specific version.
Restore a previous version​
Restoring never deletes or overwrites anything. It copies the content of an older version into a new latest version, so the full history stays intact.
- Open the test case's Change History.
- Click Restore on the version you want to bring back. The latest version has no restore action — it is already the current content.
- Confirm in the dialog.
The restored content becomes the new latest version. For example, restoring v2 while the test case is at v3 creates v4 with the content of v2. A confirmation message appears: v2 restored as the new latest version (v4). Full history preserved — nothing overwritten. All previous versions remain in the history.
Execution results keep the exact version​
Every run is permanently stamped with the exact version it executed:
- The execution record shows which version ran, for example Ran v2, and links to that version.
- Results are immutable. Editing the test case later never changes what a past run shows.
- This also applies to runs executed through the TestPak extension — it executes the version you selected, not the latest one.