Test Case Version History

Test Case Version History keeps a record of the changes made to a test case over time.

Each time a test case is saved, Endtest creates a new version containing the steps and configuration that existed at that moment. You can compare two versions, review the changes, and restore an older version when needed.

Version History is available for both Web Tests and Mobile Tests.

Open the Version History

1. Open Web Tests or Mobile Tests.
2. Open the test suite that contains the test case.
3. Locate the test case in the list.
4. Click the History button next to that test case.

The History button is displayed next to the other test case actions, before Delete.

Version History belongs to the entire test case. It tracks changes made to the steps inside that test case.

View the Available Versions

The left side of the Version History window shows the versions that are available for the selected test case.

Each version can include:

• The version number.
• The date and time when it was created.
• The user who created it.
• The number of steps in that version.
• The source of the change, such as a manual save or a restore.
• An optional change message.
• An indication of which version is currently active.

The newest version is normally shown first.

Compare Two Versions

Use the From and To selectors to choose the versions you want to compare.

For example:

• From: Version 2
• To: Version 5

Select Compare to display the differences.

The comparison is based on the logical identity of each step, not only its database row or current position. This allows Endtest to recognize the same step across multiple saves, even when the step was edited or moved.

Change Types

The comparison can classify a step as:

Modified

The step exists in both versions, but one or more of its values changed.

Examples include:

• A URL was changed.
• A locator was changed.
• The text entered by a step was changed.
• An assertion value was changed.
• An API request configuration was edited.
• A variable value was changed.

Changed values are highlighted in the comparison.

Added

The step exists in the newer version but not in the older version.

Deleted

The step exists in the older version but not in the newer version.

Moved

The step exists in both versions, but its relative position in the test case changed.

Adding another step above an existing step does not automatically mean that the existing step was moved. Endtest uses the relative order of the steps to distinguish an actual move from a normal position shift caused by an insertion or deletion.

Unchanged

The step exists in both versions with the same content and relative order.

Read the Step Comparison

The comparison presents each step in a readable format instead of showing the raw stored data.

Depending on the action, the comparison can display information such as:

• Step number.
• Action.
• Step name.
• URL.
• Target element.
• Locator type and locator value.
• Text or value.
• Variable name.
• Assertion details.
• Additional action-specific values.
• Whether the step is skipped.
• Backup locators used for self-healing.

Empty values and internal placeholder values are hidden when they do not provide useful information.

Restore an Older Version

To restore a previous version:

1. Open Version History.
2. Locate the version you want to restore.
3. Select Restore.
4. Confirm the action.

Restoring a version does not delete the newer versions.

Instead, Endtest creates a new version whose contents are copied from the selected historical version. This preserves the complete audit trail and allows the restore itself to be reviewed or reversed later.

For example:

Version 5 — Current version
Version 4
Version 3 — Version selected for restore
Version 2
Version 1

After restoring Version 3:

Version 6 — Restored from Version 3
Version 5
Version 4
Version 3
Version 2
Version 1

Version 6 becomes the current version, while the previous versions remain available.

What Is Restored

A restore recreates the test case steps from the selected version, including their:

• Order.
• Action types.
• Step names.
• Locators.
• Parameters and values.
• Skip settings.
• Backup locators.
• Other stored step configuration.

The restored steps receive new internal database rows, while their logical step identities are preserved. This allows future comparisons to recognize them as the same steps.

Concurrent Changes

Endtest can detect when the test case was changed after a user opened it.

When version conflict protection is available, a save or restore based on an outdated version can be rejected instead of silently overwriting newer work.

Reload the test case and review the latest version before saving again.

Permissions

Version History follows the same access rules as the test case.

Users who can view the test case can review its available versions. Restoring a version requires permission to modify that test case.

Recommended Practices

Review Version History when:

• A test starts failing after a recent edit.
• A locator or assertion was changed unexpectedly.
• A large test case was reorganized.
• Several users work on the same test.
• You need to understand when a configuration changed.
• You need to return to a previously working version.

For important changes, add a short change message when that option is available. A useful message explains why the test was changed rather than only describing what was changed.

Example:

Updated checkout assertions for the redesigned order confirmation page.

Important Notes

• Version History is tracked per test case, not per test suite.
• Saving a test case creates a new version.
• Restoring an older version creates another new version.
• Existing historical versions are not overwritten.
• The current version is clearly marked in the version list.
• Deleted steps remain visible when comparing with a version in which they existed.