Skip to main content

Test Case Versioning

Updated today

Overview

Vansah Test Management allows you to easily create and manage different versions of a Test Case, helping you keep tests up to date as requirements or applications change.

With Test Case Versioning, you can create and maintain multiple versions of the same Test Case. Each version can include its own updates or improvements, giving you better control and visibility over your testing process.

Key Capabilities

  • Milestone Tracking:
    Create new versions to mark important stages in your testing process. This makes it easy to track what changed and when.

  • Version History:
    Review all previous versions of a Test Case, and revert to an earlier version if needed. This ensures clear traceability and consistent Test Case management.

  • Parallel Execution:
    Keep multiple versions active at the same time across different Test Types. This lets you run and manage separate test versions independently.

Creating Test Case Versions

A Test Case Version is composed of the following fields on a Test Case:

Test Specification:

  • Test Headline

  • Test Description

  • Test Script

  • Test Type

  • Custom Fields

  • Attachments

Each Test Version can be identified by a user-defined name. When initiating new versions, users have the freedom to explicitly designate the names for the versions. Additionally, the system allows for the renaming of existing versions.

To initiate a new version:

  • Select the “+ Create new version” option from the Actions menu located adjacent to the version number in the top right corner of the Test Case.

A dialog window will be displayed, enabling you to define the version name and select a base version from which to create the new Test Case version. Additionally, you will have the option to designate the new version as the Default version.

The Default Version

The Default Version is the main or baseline version of a test case. It represents the officially approved or reference version that should be used across projects or test plans unless another version is explicitly selected as the active version.

Typically, this is the version that is linked to any requirement and it is considered the Active for Test Execution. When a Test Case is updated (for example, new steps added or data changed), the previous version remains as historical reference, and you can choose to promote the new version as the Default once validated.

To designate the default version:

  • Select the “Set default” option from the Actions menu positioned next to the version number (see: Manage Test Case Versions)

Active Version:

The active version is the current version being executed or validated against the requirement. You can create newer versions of the same Test Case (e.g., to reflect feature changes or fixes) and set one as Active. Vansah will always use the Active version during test execution (in Test Runs, Test Plans, etc.).

Lets take the following example:

Requirement: Jira Story “Create an Admin Authentication”
Linked Test Case: TC-1234 which has the following versions:

Version

Status

Description

V1

Designing Test Case

V2

Added Test Steps

V3

Default

Approved Test Case version. This version will be used when linking the Test Case to any new requirement or Test Plan.

V4

Minor changes.

V5

Active

Updated version reflecting recent authentication flow changes.

Viewing Test Case Versions

To transition between Test Case versions, simply follow these steps:

  • Click on the versions dropdown selector located in the top right corner of the Test Case interface.

  • Select Manage Versions

Archiving Test Case Versions

Test Case versions can be archived and unarchived as needed. Once archived, these versions are no longer executable and are maintained purely for historical record-keeping purposes.

You can only archive a Test Case version if it is not the default or only version of the Test Case.

You can restore any Archived version by selecting it and clicking on Restore


Did this answer your question?