Hi,
We are migrating from Xray to Zephyr Squad. We use eazyBI for reporting from Xray but now need to point it at Zephyr. Does anyone have any advice they can pass on about how best to repoint eazyBI from Xray to Zephyr? What works, what doesn’t work, what to avoid, etc.
Thanks in advance,
Adam
Hi @sterra
The dimensions and measures are different between Xray and Zephyr apps, so this won’t be a simple “repointing” - you’ll need to rebuild the reports. You can make a layout in which Xray dimensions and measures should be replaced with the more or less equivalent Zephyr dimensions and measures
Unfortunately, there are currently many variations of Zephyr apps with shared names but differing functionality. Which Jira platform (Cloud or Data Center) and Zephyr product combination are you using?
- Zephyr Squad (legacy version) on Cloud, which is no longer available in the Atlassian Marketplace. You can build reports on the testing data in eazyBI: Zephyr Squad Test Management for Jira .
- Zephyr Essential on DC or Zephyr Squad (legacy version) on DC, which currently hides under the new name Zephyr Essential, but has the same functionality as before. You can build reports on the testing data in eazyBI: Zephyr Squad Test Management for Jira .
- Zephyr Essential on Cloud - the functionality differs from DC. This integration is not yet supported in eazyBI; we are looking forward to implementing it, but I can not provide an exact timeline.
- Zephyr (former Zephyr Scale) on DC or Cloud. You can build reports on the testing data in eazyBI: Zephyr Scale Test Management for Jira .
Based on the combination of Jira and Zephyr, a different set of measures and dimensions will be available for your reports, representing similar entities from Xray.
Best,
Zane / support@eazybi.com
Hi Zane,
Thanks for your reply. We are using Jira Cloud Enterprise version, and we are required to migrate to Zephyr Squad. This is part of a bigger migration of all the separate sites in the Enterprise cloud to a single site on the Enterprise cloud.
Regards,
Adam
It looks like you have previously installed the Zephyr Squad app on your Jira Cloud for some other projects, as you have the option to get this legacy version.
While both apps use issues as the Tests, there are many differences that can not be directly transformed.
Main measure mapping from Xray to Zephyr Squad dimensions
- Xray Test → Issue dimension, use in combination with Issue Type dimension to specify Tests.
- Xray Test Execution → Zephyr Squad Test Cycle
- Xray Requirement → Can use a workaround by importing issue links
- Xray Test Plan → N/A
- Xray Test Set → N/A
- Xray Test Pre-condition → N/A
- Xray Defect → Zephyr Squad Defect
- Xray Defect Priority → Can use workarounds with calculated measures
- Xray Defect Status → Can use workarounds with calculated measures
- Xray Test Run Assignee → Zephyr Squad Test Assignee
- Xray Test Executed by → Zephyr Squad Test Executed by
- Xray Test Run Status → Zephyr Squad Test Status
- Requirement Status → Can use workarounds with calculated measures
- TestRunStatus → N/A
- Xray Pre-condition Type → N/A
- Xray Test Type → Import cutom field Zephyr Test Type
- Xray Test Execution Test Environment → N/A, can make some calculations using property “Zephyr Squad Test Cycle environment”
- Revision → N/A
Main measure mapping from Xray to Zephyr Squad measures
- Xray Tests created → Zephyr Squad Tests created
- Xray Tests defect count → Zephyr Squad Tests defect count
- Xray Tests scheduled → Zephyr Squad Tests scheduled
- Xray Tests executing → Zephyr Squad Tests executed, use with dimension Zephyr Squad Test Status and choose specific statuses like WIP
- Xray Tests executed → Zephyr Squad Tests executed, use with dimension Zephyr Squad Test Status and choose specific statuses like PASS, FAIL
- Xray Tests with executions → Zephyr Squad Tests with executions
- Xray Test Runs → Zephyr Squad Test Execution count
- Xray Tests execution summary → Can use workarounds with calculated measures
- Xray Test Executions created → Can use workarounds with calculated measures
- Xray Tests executed first date, Xray Tests executed last date → Workaround: Can recreate with calculated measure
- Xray Requirements created → N/A, Workaround: import issue links and make calculated measures that count linked issues
- Xray Test Runs created first date, Xray Test Runs created last date → N/A,
- Xray average Test Run duration, Xray Total Test Run duration → N/A
Main measure mapping from Xray to Zephyr Squad properties
- Xray Test last executed date → Zephyr Squad Test last executed date
- Xray Test last executed by → Zephyr Squad Test last executed by
- Xray Test last execution status → Zephyr Squad Test last execution status
- Xray Test Execution Begin Date → Zephyr Squad Test Cycle start date
- Xray Test Execution End Date → Zephyr Squad Test Cycle end date
- Xray Test Execution Revision → N/A
- Xray Test Execution Test Environments → Zephyr Squad Test Cycle environment
- Xray Defect status → Zephyr Squad Defect status
- Xray Defect priority → Can use workarounds with calculated measures
- Xray Defect created → Zephyr Squad Defect created
- Xray Defect assignee → Zephyr Squad Defect assignee
- Xray Execution Test Plans → N/A
- Xray Test Test Plans → N/A
- Xray Test Test Type → Can use workarounds with calculated measures
- Xray Test Cucumber Test Type → N/A
- Xray Test Plan Begin Date → N/A
- Xray Test Plan End Date → N/A
In conclusion:
-
Zephyr Squad has less information, and some of the Xray reports might not be replicable. For example, anything related to Test Plans
-
Unfortunately, the “find and replace” approach won’t work, as each of those options should be reviewed if the report can be recreated.
-
Some of the fields could be replicated with calculations, some simple (like retrieving properties or getting execution summary), and some complex (first and last execution dates or requirement count).
-
Good news, Test custom fields can be imported as custom field dimensions and used for your Zephyr Squad reports.
Best,
Zane / support@eazyBI.com
Fantatsic.
Thanks Zane.