Page History
...
- Zephyr >= 4.0.0
- Zephyr and Xray should be both installed
- project where migration is being done must have Xray issue types (at least the Tests, Test Executions and Test Plans)
- you may use the "Add Xray Issue Types" action shortcut available in the project settings page
- requirement issue types used in Zephyr must be configured in Xray
- all the different issue types that Zephyr Tests cover should be configured in Xray's Issue Type Mapping settings.
- defects 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 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 sure Zephyr is using different issue links between Test<=>Defect and Test<=>Requirement, by going into Zephyr's configuration settings
...
How it works
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)
Test Execution, linked to the previous Test Plan
| |
Execution
| Test Run
|
| Info | ||
|---|---|---|
| ||
All issues will be created in the project where the migration is being performed. |
...