Test Repository Module Migration

Test Cases and Folder Structure

The test case folder structure for each release in Zephyr Enterprise will migrate to QMetry at the project level. Each release will become a parent folder; the original hierarchy will remain intact in the corresponding release folder.

In Zephyr Enterprise, test cases are linked to a specific release.
In QMetry, all test cases appear at the project level. Test cases are arranged in a project according to the release folder and subfolders. You can view the release linked to each test case in the Release and Cycles section of the test case details.

Note

Test cases linked to multiple releases in Zephyr Enterprise will migrate to QMetry and appear in various folders. Each instance will align with the appropriate release folder hierarchy.
Test cases not linked to any release in Zephyr Enterprise will be placed in a project-level folder in QMetry.

Test Case

The following is the test case migration approach:

All test cases and step attributes will be migrated. Zephyr Enterprise system attributes not available by default in QMetry will be migrated as user-defined fields.
All versions of each test case in Zephyr Enterprise will be migrated to QMetry.
Test case attachments in Zephyr Enterprise will migrate to the corresponding test cases in QMetry.
Requirement-to-test case mappings in Zephyr Enterprise will migrate to the latest version of each test case in QMetry.
Test Case Priorities are migrated as follows:
Zephyr Priority
QMetry Priority
P1
Blocker
P2
Critical
P3
Major
P4
Minor
P5
Trivial
In Zephyr Enterprise, the estimated time for the test case is recorded in the format HH:MM:SS: SSS. In QMetry, it is stored as HH:MM: SS.During migration, any estimated time under one second will be rounded to the nearest whole second in QMetry.
Releases and cycles from Zephyr Enterprise will be mapped to test case versions in QMetry as follows:
- If a test case version is planned or scheduled for execution in a release and cycle in Zephyr Enterprise, the same release and cycle will be linked to that test case version in QMetry.
- If a test case exists only at the project level in Zephyr Enterprise, it will not be linked to any release or cycle in QMetry.
- If a test case is part of a release in Zephyr Enterprise but is not planned or scheduled for execution in any cycle, it will be linked to the default cycle of that release in QMetry.
- If multiple test case versions are planned for the same cycle in Zephyr Enterprise release, only the latest version will be linked to the corresponding release and cycle in QMetry.
In Zephyr Enterprise, different test case versions can be linked to requirements across multiple releases. During migration to QMetry, all such requirement associations will be consolidated and mapped to the latest version of the test case.

Zephyr Priority	QMetry Priority
P1	Blocker
P2	Critical
P3	Major
P4	Minor
P5	Trivial

Call to Test

In Zephyr Enterprise, a test case can be invoked in another test case as a Call to Test, and the called test functions are a step in the parent test case.
In QMetry, the feature is a Shareable Test Case, which can be referenced as a step in other test cases.

Migration Approach

All Call to Test instances from Zephyr Enterprise will be migrated as Shareable Test Cases in QMetry. These shareable test cases will be inserted as steps in their corresponding parent test cases.
When a test case version is used as a Call to Test in another test case in Zephyr Enterprise, a copy of the test case, including all its versions, is created in QMetry as a Shareable Test Case. This shareable test case is then referenced in the respective versions of the parent test cases.
In scenarios with multiple levels of nesting, such as when a called test case contains another Call to test:
- A shareable copy is created only for the directly referenced test case.
- For dependent steps that originate from another called test case, the relevant steps will be included directly in QMetry, without creating an additional shareable Test Case.

Test Case Parametrization

All parameters defined at the Zephyr Enterprise global or test case level will be migrated to the Instance level in QMetry.
In QMetry, these parameters will be linked to their respective projects based on their project associations in Zephyr Enterprise.
Duplicate parameters, if any, will have their values consolidated into a single parameter.
While migrating parameterized test cases from Zephyr Enterprise to QMetry, all parameters used in the test case steps will be consolidated and listed in the enter Data field of the first step in QMetry. Their references will be retained throughout the step details.
In QMetry, parameters are referenced using @parametername in test case steps. Parameter grids can be defined at the project level or directly during test suite executions.
The data grid linked to a test case in Zephyr Enterprise will be associated with the corresponding test case during its execution in QMetry.

In this section: