Page History
...
As of Xray v3.3, the importer only performs inline migration of data (i.e. Zephyr's Test issues are "moved" to Xray's Test issues).
Before using the
...
Zephyr Import tool
Before using the tool, please check the necessary requirements and also the existing features and its limitations.
...
- Zephyr >= 4.0.0
- Zephyr and Xray should be both installed
- project Project where migration is being done must have Xray issue types (at least the Tests, Test Executions and Test Plans)
- You
- you may use the "Add Xray Issue Types" action shortcut available in the project settings page
- requirement Requirement issue types used in Zephyr must be configured in Xray
- all All the different issue types that Zephyr Tests cover should be configured in Xray's Issue Type Mapping settings.
- Defect issue types used in Zephyr must be configured in Xray
- All the different issue types are being used as defects in Zephyr should be configured in Xray's Issue Type Mapping settings
- Create create similar Test Statuses and Test Step Statuses in Xray; this is not mandatory but may ease the process, which will always ask you to make the mapping between Zephyr statuses and Xray counterparts
- make Make sure Zephyr is using different issue links between Test<=>Defect and Test<=>Requirement, by going into Zephyr's configuration settings
- Do not change, create or delete any issue in the Project while the importation is running
- The only mandatory field in Xray's Test, Test Execution and Test Plan should be the issue Summary and issue Reporter
- Make sure that the Jira workflow states, that are being used by "Zephyr Test" issue type, are editable. Click here for the official Jira documentation on this subject.
- We strongly recommend you to make a backup of your Jira instance before doing the importation
Info | ||
---|---|---|
| ||
The current process performs an inline migration, i.e. Tests and data is migrated to Xray and the original entities are "lost". Thus, we recommend to backup your JIRA Jira instance before performing the migration. Also, as the amount of data to migrate may be considerable large, we advise you to perform this on non-working hours. Please also make sure that users are not changing data on the project while the migration is being done. |
...
Most information will be migrated seamless seamlessly but please check the following table in more detail.
...
Supported Features | Unsupported |
---|---|
Inline migration (not cloning) of:
(*) Cycle folders will be migrated to Test Executions, since the semantics on Xray are a bit different in terms of entities/organization. |
|
(*) Cycle folders will be migrated to Test Executions, since the semantics on Xray are a bit different in terms of entities/organization. |
How it works
Notas
- quando a coluna do Step está vazia <undefined>
- all issues will be created within the same project where the migration is being done
Recomendações
- criar os mesmos estados no Xray antes da migração
- links diferentes Test<=>Defect Test<=>Requirement
- backup Jira before migrating
- After working hours (as it can be intensive)
O que migra
...
- plus 1 Test Execution (Executions soltas)
Within this section you're able to find the exact mapping of entities from Zephyr to Xray.
Mapping of information
Zephyr entity | Xray entity | Notes |
---|---|---|
Test
| Test
|
|
Cycle | Test Plan (optional)
Test Execution, linked to the previous Test Plan
| The Test Execution created here will contain the Executions assigned directly to the Cycle, since in Zephyr you can have Executions at that level besides on each folder. Please note that...
|
Cycle's folder | Test Execution, linked to the Test Plan created earlier from the Cycle
|
...
|
...
| |
Ad-hoc Cycle |
...
Test Plan (optional) |
- plus 1 Test Execution
...
Test Execution, linked to the previous Test Plan
| |
Execution
| Test Run
|
fixVersion é inferido da versão atribuída ao cycle
Test Plan
<version> - <cycle's name>
Requisitos iniciais
Pós-operações
...
Info | ||
---|---|---|
| ||
The current importer is relatively basic. If you need to migrate more information and have further control over the migrated data, we recommend you contact an Atlassian partner with expertise on this kind of migrations. Note that migrating "all" information may be a complex process to implement and some things may not be mappable at all. |
Info | ||
---|---|---|
| ||
|
How to use
Suppose you have a project in HP ALM (see above for supported version/s) and you wish to import the tests from HP ALM's "Test Plan", as seen below:
All issues will be created in the project where the migration is being performed. |
How to use
Performing the migration is easy; however, it is currently limited to Jira administrators.
The migration follows a wizard like interface; after going through the steps, some additional tasks required to ensure consistency of data.
Performing the migration
Suppose you have a project that you wish to migrate from Zephyr for Jira to Xray and that the requirements mentioned above are met.
To start the importation process:
- Log in with an administrator account.;
- Go to System>Import and Export>External System > Import and Export > External System Import.;
- Select Xray's HP ALM/QC Importer.
Then, you need to fill out the details of the HP ALM/QC instance, including its host name/IP, port, domain, project and authentication credentials.
Upon successful connection, you can optionally define a label to assign to the Test issues that will be created. This may be quite useful if you need a quick way to identify the newly created issues. The label syntax is restricted in the same way as the label fields in Jira. We recommend using a unique label with numbers.
- s Zephyr for Jira Importer.
If you see the following error message, then it's because Zephyr is using the same issue link types between Test<=>Defect and Requirement<=>Test.
Xray needs have different relations, so that is able to understand the different cases. Thus, you need to change the "Linktype for Test → Relation" to something different from the value "LinkType for Requirement → Test". For example, you can leave "LinkType for Requirement → Test" with "Relates" and change the "Linktype for Test → Relation" to "Defect".
These relations are configurable in Add-ons > Zephyr for Jira > General Configuration > Issue and Remote Links Configuration.
After ensuring that the link types are configured with distinct values, you may proceed once again with the migration process.
The importer will show you some brief information, that we advise you to read carefully.
Then, you need to choose the project in which you want the Test issues to be created.where to perform the migration; this will be same where the Xray entities will be created in.
You may fine-tune the process by (un)checking some flags:
- Links between requirements and tests to respective Xray Issue Link Type used for requirement coverage: creates the link Xray uses for tracking coverage between Tests and requirements; by default Xray used the "tests" issue link type
- Zephyr Cycles to Xray Test Plans: creates Test Plans based on Zephyr Cycles
- Zephyr Ad Hoc Cycles to Xray Test Plans: creates Test Plans based on Zephyr Ad Hoc Cycles
If Zephyr Cycles to Xray Test Plans and Zephyr Ad Hoc Cycles to Xray Test Plans are unchecked then no Test Plans will be created; nevertheless, Test Executions will always be created if Zephyr Executions exist.
You need to map Zephyr's Test Statuses to Xray counterparts.
Likewise, you also need to map Zephyr's Test Step Statuses.
A final confirmation dialog presents information about the total number of Tests Xray entities that will be imported.This number may be lower created.
than the actual number of Test issues that will be created; this occurs because Xray will only be able to import some of the tests, depending on their characteristics which can only be determined during the actual importation.
At the end, a brief summary is shown mentioning the total number of Test Xray issues created and any warnings that occurred during the process.
Please have a look at the following section for some additional steps before concluding the migration process.From this screen, you can also see the list of created issues based on the label you provided. You can also consult the detailed logs about the process.
After doing the migration
After migrating data from Zephyr to Xray you will need to perform some additional operations to recalculate the status of Tests and the coverage of the related requirements.
- reset the "TestRunStatus" custom field of the migrated Tests
- you can use the link provided in the final screen mentioned earlier for quickly obtaining the created Tests; you will be redirected to the Issues search page
- save this search as a filter (you will need it afterwards)
- do a bulk change operation on the Test issues
- reset the TestRunStatus custom field
- you can use the link provided in the final screen mentioned earlier for quickly obtaining the created Tests; you will be redirected to the Issues search page
- reset the "Requirement Status" custom field of the requirements linked to the migrated Tests
- use the testRequirements JQL function using use the name of the previously saved filter as argument
- do a bulk change operation on the requirement issues
- reset the Requirement Status custom field
- use the testRequirements JQL function using use the name of the previously saved filter as argument