Requirement Versions and Test Case Versions
Create multiple versions of a test case or requirement during editing. The system displays all available versions of an asset at the top of the details page.
To view version details, perform these steps:
Open the module details page.
Click the Version drop down at top right corner of the page.
The Versions drop-down displays all existing versions of the requirement. Select any version to view its details, and the currently viewed version is highlighted.
Scenario | Version Information / Syntax |
New Requirement or Test case | Version No. (Creator, Version Creation Date) |
Updated Requirement or Test Case | Version No. (Version Name, last modified by User, last modified Date) |
Requirement or Test Case Updated without Version Name | Version No. (last modified by User, last modified Date) |
User is Deleted | Version No. (Version Name, last modified Date) |
Note
If the last editor of a requirement is deleted, the version owner field becomes blank.
Creating a New Version of the Test Asset
 |
When you edit or add steps to an executed test case, you can save it as a new version.
Updating overwrites the old details, but creating a new version retains the original values and lets you reuse the test case.
Note
Permissions
Ensure your role includes versioning rights.
The is visible only for users having versioning rights.
Admin can configure versioning rights from Customization under Roles.
To create a new version of a test case, perform these steps:
Go to the Test Case Module.
Access Create a New Version from:
Click the Cog (⚙️) icon for the test case and select Create New Version.
Open the Test Case Detail Page and click Create New Version iconon the header.
Make the necessary edits and click Save as New Version.
Creating a new version saves your changes. But the existing test suites continue to use the previous version.
Managing Execution Status When Saving a New Test Case Version
When saving a new version of a test case that has been previously executed, you have two options:
Auto Sync Latest Version: The test case version is updated and the execution status resets to Not Run.
Example 20. Execution StatusIf TC1 had a Passed status in TS1, and the user creates a new version of TC1, then TS1 will display TC1’s status as Not Run.
Manual Sync:Click the sync icon to update the latest version.
Note
The synced version does not display previously linked issues.
After syncing, the execution status of the test case changes to Not Run.
Any new test steps added in the latest version are reflected on the execution screen.
You can use different versions of a test case for testing.
Associate Version with Release and Cycle
Associate a version with current scope as well as other scopes. While associating requirements or test cases with release and cycle, you can select the version of the entity which is to be associated with the selected release and cycle.
Editing Version Details
To edit the version details of a test asset, perform these steps:
Open the module details page or edit page.
Open the Version tab.
It displays details like - Version Summary, Version number, Cycle with which it is associated, Updated On and updated by user.
Edit the version name by clicking on the name.
Deleting a Version
Archive and delete individual versions of a requirement or test case.
Archiving a Version
To archive a test case or requirement version, perform the following steps:
Go to the test asset details page.
Select the Version tab to view different versions.
The Action column has and .
To archive a particular version, click Archive.
Attachments, test cases, requirements, issues, releases, and cycles can not be added to the archived requirement or test case.
Note
You can Delete a version only after archiving it.
Deleting a Version
To delete a version, perform these steps:
Expand the filters and select Show Only Archived option.
Click Delete to delete a particular version of the asset.
To unarchive an archived test case or requirement, click .