Automated Steps Library and enhanced editing of Cucumber Tests/Pre-Conditions
Move data/restore projects between Jira instances
Column
width
60%
For restoring projects,Jira offers the built-in "Project Import" tool which allows partial, project imports (i.e. importing a specific project from a previous backup).
This tool has some limitations though; it cannot transfer apps/add-ons related data between instances unless apps are prepared for it.
Fortunately, since v3.3, Xray is able of taking advantage of this mechanism; on previous versions, issues would be restored but the testing data wouldn't.
Thus, you can now use built-in backup&restore facilities of Jira:
for copying a project from one Jira instance to another Jira instance (e.g. from staging to production, or from internal to a DMZ instance)
to restore a project upon some mistake/data loss has been done in that project within an existing Jira instance
If you've adopted BDD and Cucumber, the number of Cucumber Scenarios/Backgrounds will increase as your project grows. Since Cucumber steps can, and shall, be used across different test specifications, you may need to do some refactoring on your existing steps to avoid duplicates and foster reusability.
The Automated Steps Library provides a central place to view and manage all the Cucumber steps used in the context of a given project. This will allow you to classify/label steps, refactor them (update, merge), and quickly identify the entities that use them.
Steps are added automatically to the Automated Steps Library when Tests or Pre-Conditions are created or updated. Once in the library, they can be used to create/update Cucumber Tests/Pre-Conditions, using autocomplete and filtering steps based on labels.
You can now be much more efficient using the enhanced editor for Cucumber based Tests/Pre-Conditions right inside Jira.
Integration with Apwide Golive (previously "Apwide Test Environment Manager")
Built-in Zephyr migration utility
Column
width
40%
Column
width
60%
Xray provides you with powerful capabilities to analyze test results and coverage on a per Test Environment basis. You can easily understand how tests and requirements are faring on specific target environments.
To answer the needs of our customers dealing with many Applications and Test Environments, we have built an integration with Apwide Golive, a Jira app with advanced Environment and Release Management functionalities.
On Xray screens, the QA team knows as soon as an Environment becomes unstable or when the wrong version of an application is deployed. Efficiency increases with clickable links to access the Environments and the possibility to book dedicated Environments for test campaigns.
Test Executions and Test Plans are now planned on a Timeline with drag-and-drop and Xray issues dates are automatically updated. Jira filters can be used to obtain a real-time list of bugs that can be tested on a specific environment, taking into consideration the deployed version and the environment status. You can easily understand how tests and requirements are faring on specific target environments.
New gadgets: Requirements List and Overall Test Results
Column
width
60%
Two new gadgets to track QA progress in your Jira dashboards: Requirements List Gadget and the Overall Test Results Gadget.
The Requirements List Gadget provides an enhanced list of requirements, including hierarchical information (e.g., Epic > Story), along with completeness information and respective number of Tests, analyzed in the context of some version or Test Plan. This information is similar to the one seen at the end of the page in the Overall Requirement Coverage Report whenever drilling-down on some requirements.
The Overall Test Results Gadget provides an overview of the status of Tests, in the context of a version or Test Plan. Thus, you can see the number of Tests that passed or failed, displayed in a pie chart or in a table layout.
Learn more about these and all other gadgets here.
