Test Case Versioning Overview

Zephyr's test case versioning provides a unique solution to managing test case versions when updated changes are made to an individual test case and its fields.

Test case versions are updated incrementally when changes are made to any fields for the individual test case. For example, if a user changes the name of the test case or description, the version will be updated incrementally to accommodate the changes.

Zephyr allows users to compare different versions of a test case to distinguish the changes that are made.

Zephyr provides the full functionality to use any test case version with the simple click of the mouse. Users can roll back or switch to any test case version they want when previewing the different versions in the table view.

How Version work on Zephyr Enterprise

We will refrain from creating a new version if a test case is not utilized anywhere, such as in a different release or project or the planning phase. In this scenario, the user will continue using the current version of the test case. Additionally, if the test case is already the latest one available, we will not increment its version number.

Best Practices

Test case versioning allows users to use different versions of a test case. They can use the most up-to-date version or an older version.

For example: If a test lead creates the initial test case to be used for testing and then tester one decides to update and change the description of a test case, the version of the test case will change incrementally. The initial version of the test case was version 1 but after the changes, the version will be updated to version 2.

This is beneficial because it allows users to view the details of a previous version of a test case, compare any two versions of a single test case, and rollback their test case to a previous version.

Test Case Version Incrementing

• When a test case is created, its default version is 1. When updated, the version is updated incrementally by 1.

Open

• The test case has not been utilized anywhere in this scenario. Therefore, modifying the details of the existing test case will not result in a version increase.

Open

• When sharing the test case with another project, release, or the project repository, the version will be incremented upon updating it.

• When a test case is shared from the global test repository to a release/project repository and then updated, the version will be increased incrementally.

Open

• If the version colour is orange, it indicates that you are not using the latest version. The version will be incremented after the test case is updated.

Open

• The version will remain unchanged upon updating the attachment and requirement mapping, and these modifications will be reflected in all versions of the test cases.

• If we apply the "use this version" to the previous iteration and then make any modifications to the test case, the version of the test case will increment, which may not reflect the most recent changes.

Open

• When a test case scheduled in a test cycle is edited or updated, a new version is created, and if the same test case is edited, Zephyr updates the same version.

Open

• When a test case is shared with the project repository and updated on a release/project repository level, the version will be increased incrementally.

• When editing a test case in a cloned release, the version will be increased (if the cloned release is within the same project or the cloned release is from a shared project).

• If the test case is planned more than one time for the execution on editing the test case, the version will increase (Restrict editing a test case version that has already been executed is true or false)

• Restrict editing a test case version that has already been executed is true.

  • If the test case is planned one time but not executed, then on editing, it will not increase the version.

  • If the test case is planned one time and Executed, then editing will increase the version.

• When using "Use this version" to a previous test case version, the version will be increased if any changes are made to the test case afterwards.

• When using "Use this version" for a test case within a shared project, if the shared test case is updated, the version will be increased.

Test Case Version within Test Planning

• After scheduling a test case and if changes are made in the test repository, the version of the test case in the test repository will be increased.

• If an already scheduled test case is in a phase/cycle, any changes made to the test case in the test repository will not be reflected in the test planning/execution until the test phase or execution is synced.

• When adding a test case from another test cycle, there are 2 options provided for the test case version used:

  • Get Linked Version: This will fetch the test cases with the version available from the original test cycle.

  • Get the Latest Version: This will fetch the test cases from the original test cycle and then retrieve the latest version of the test case from the test repository.

• When syncing:

  • When a test case is executed: The sync will not update the test case details if it's already executed, and the version is not updated if "Mark as not executed for the executed test case of latest version" is not checked.

  • When a test case is executed, the sync will update the test case details if it's already executed, and the version will be updated if "Mark as not executed for executed test case of latest version" is checked.

  • When a test case is unexecuted: The sync will update the test case details for unexecuted test cases (this will update the details to the current version of the test case from the test repository).

Test Case Version when Exporting

• When exporting from the test repository/search windows, Zephyr will always export the current version of the test cases in the test repository.

• Zephyr will always export the linked version of the test cases when exporting from the test planning.

• When exporting from test execution/search, Zephyr will always export the linked version of the test cases.

Test Case Version when Cloning a Release

• When cloning a release within a project, the test case ID of the test case will not change, and all the test case versions will be available for the cloned release.

• When cloning a release across a project, if the project has shared access to the original project, the test case ID will remain the same, and all versions of the test case will be available for the cloned release.

• When cloning a release across a project, if the project does not have shared access to the original project, a new test case ID will be created with the default version of 1.

Test Case Version Limitations

• Requirement to Test Case mapping will not be versioned.

• Adding an attachment will not increment to a new version for a test case.

• If a user deletes a custom field, the user cannot revert back to the older version of a test case that had a value for the deleted custom field.

  • The user will not be able to see the deleted custom field.

• If a project isn't shared, the user clones a release within the project, and after upgrading, the user will get different test case IDs.

Test Case Version when Sharing Limitations

• Shared test cases are not editable when a user can't access the original project.

• Users cannot add an attachment if they don't have access to the original project.

• A project cannot be unshared if it has a shared test case or a test case shared from a different project/release.

• Users cannot share the same test case ID multiple times within the same release because the test case ID is unique on the release level.

• Users cannot delete a project if the project has a test case that is shared.

• Users will not be able to view the custom field for a project-specific test case shared in the grid column.

View Test Case Versions

1. To view the different versions of a test case, simply click on the individual test case for which you want to preview the versions. There should be a "Version" field at the top-right of the interface. 

2. click the "Versions" button to bring up the modal that displays the different test case versions.

Open

3. After clicking the "Versions" button, the modal should appear, showing a table with the different test case versions. The test case versions table will display the following fields:

• Version Number

• Name of the Test Case

• Alt. ID (If there is one given)

• M/A - Whether the test case is manual or automated.

• Last Updated By - The last person to update that version)

• Last Updated On - The last date the test case was updated on.

• Created On - The initial date the test case was created on.

• Action - Displays which version is the current version and will display "Use This Version" for all other versions. Zephyr allows users to switch the test case to a different version whenever by simply clicking on "Use This Version" for the version they want to use. This will change all the fields for the test case to match the fields of the selected test case version.

Open

4. To preview an individual version of a test case, the user must click on the individual version in the table. 

• This will display all the details of the test case corresponding to the version clicked.

Open

Compare Test Case Versions

1. To compare test case versions, the user must bring up the test case version modal, which displays the different versions of the test case.

2. Naturally, users can then select which two different versions of a test case that they want to compare by utilizing the checkboxes on the left-hand side of the table view for the test case versions.

3. After the versions are selected, users must click on the "Compare" button at the top left of the modal to begin comparing the two versions.

Open

4. The compare version modal will appear, depicting the two different versions side-by-side in one window to allow the user to visibly preview both of the versions at the same time.

• Zephyr provides a side-by-side comparison when viewing the two test case versions, allowing your users to quickly distinguish the changes made between the two different versions.

• The left side will display the first version, while the right will display the selected second version.

• When comparing different versions, Zephyr will highlight areas and fields where there are differences. This is quite useful for users because they can visibly see the changes right away, reducing the time spent looking for the changes between the versions.

Open

Back to Top ^