Q13 of 14 · JIRA
What is Zephyr for JIRA, and how does it differ from Xray?
Short answer
Short answer: Zephyr Squad (for JIRA Cloud/Server) adds Test and Test Cycle issue types inside JIRA, similar to Xray. Key differences: Zephyr uses Cycles rather than Test Plans for grouping, has tighter native JIRA integration, while Xray has a broader automation ecosystem and Cucumber/CI integration.
Detail
Zephyr Squad key concepts:
- Test — same as Xray: a single test case with manual steps or linked automation.
- Test Cycle — a time-boxed execution of a group of tests (equivalent to Xray's Test Execution). Cycles are associated with a version and can be cloned for repeat testing.
- Test Execution — a single test-to-tester assignment within a cycle (called an "execution" in Zephyr, but it's not the same level as Xray's Test Execution issue type).
Comparison:
| Feature | Xray | Zephyr Squad |
|---|---|---|
| Issue types in JIRA | Yes | Yes |
| Test Plan / Cycle grouping | Test Plan → Test Execution | Version → Test Cycle |
| Cucumber integration | Native, REST API | Via Zephyr Scale (paid upgrade) |
| JUnit/TestNG XML import | Yes | Yes |
| Coverage on Stories | Yes (Test Coverage panel) | Yes (Test panel) |
| Reporting | Robust, built-in dashboards | Basic; Zephyr Scale has more |
Zephyr Scale (the enterprise successor to Zephyr Squad) is a separate product with more robust reporting and CI integration, but is priced separately from the base JIRA licence.
Practical advice: If your team already uses Cucumber or Playwright and wants CI results imported automatically, Xray has better out-of-the-box integration. If the team primarily runs manual test cycles with occasional automation, Zephyr Squad is simpler to set up.