23 March 2016
The Xray for JIRA team announces the release of Xray 2.1.0. Version 2.1 contains lots of new features as well as bug fixes. Please check the highlights bellow.
Highlights for this release
New Reports
Xray now provides new reports as well as a new landing page for all reports in Xray. More reports are coming in the future.
New Report Landing Page
Within the project context left bar, you will see a new icon with the Xray symbol. This will take you directly to the reports page with the last report you used already selected. From here, you will be able to change to any of the provided reports. You can also find the Requirement Coverage reports here. The old project shortcut to access the requirement coverage reports through the project add-ons is deprecated and will be removed in future releases.
Traceability Matrix Report
This report allows users to analyse the requirements and their traceability to tests, runs and defects.
Some possible usage scenarios:
- make full traceability analysis, from requirements<=>Tests<=>Test Runs<=>Defects
- evaluate the requirement status for a given version and see all linked (open/closed) defects
- see the tests covering each requirement and all their runs and how that contributes to the overall requirement status
- analyse the requirements and related executions and respective defects, in a context of a given Test Environment
- see what defects are impacting the requirements, or a subset of the requirements of a specific version
Test Plans Report
This report allows users to evaluate some relevant metrics of Test Plans and, eventualy, compare with other Test Plans.
Some possible usage scenarios:
- analyse both the progress of the Test Plan and the success rate (i.e. the % of Tests contributing to the requirement's OK status)
- analyse the success rate by Test Environment
- see the amount of manual Tests vs others in the Test Plan
- see the overall execution status (i.e. the latest status of the Tests of the Test Plan)
- see the amount of linked defects, in the context of the Test Plan, currently opened/closed
Test Executions Report
This report allows users to evaluate some relevant metrics of Test Executions and compare them between different cycles.
Some possible usage scenarios:
- analyse both the progress of the Test Execution and the success rate (i.e. the % of Tests contributing to the requirement's OK status)
- see the amount of manual Tests vs others in the Test Execution
- see the overall execution status (i.e. the current status of the Test Runs)
- see the amount of linked defects, in the context of the Test Execution, currently opened/closed
Test Runs Gadget
See the overall status of scheduled/executed test runs (e.g. from a test plan), grouped, in order to be able to evaluate the testing effort and the planned/executed runs for certain parts of the system.
Some possible usage scenarios:
- analyse the Test Runs from a Test Execution
- analyse the Test Runs from all Test Executions belonging to a Test Plan
- depict the testing results for a given component, in the context of a Test Execution or Test Plan
- see how the testing "progress", in terms of scheduled runs, is from the Test Run assignee perspective
- see how the testing "progress", in terms of scheduled runs, is doing, by Test's priority
- see how failures, or some other test run statuses, are impacting components
- analyse the Test Runs of a given Test Environment
Automation, Automation, Automation
Xray now natively supports the import of Tests and their results from many different automated test frameworks, through specific REST API endpoints that are able process JUnit, Nunit, Robot framework result reports.
All fully documented, with some simple tutorials including Selenium, Rspec, GoogleTest, PHPunit, pyunit, SoapUI, CasperJS, Mocha, Minitest, etc.
Learn more here.
Automation specific documentation
Xray was born having in mind automated testing. From day 0.
Therefore, we created a brand new "Automation" section in our documentation, detailing the whole process and including many tutorials for different languages (C, C++, C#, Java, Javascript, Ruby, Perl, Python, PHP, etc) and automated testing frameworks and libraries, including Selenium.
Now you will have some high-quality reference documentation, so nothing stops you from starting doing test automation and have their visibility in JIRA.
Learn more here.
Analyse Test and Requirement status by Test Environment
Now you can analyse the status of your Requirements, Tests and Test Sets for a specific Test Environment. Besides Version or Test Plan, you can now also choose the Test Environment in the following reports/sections:
- Requirement Coverage reports
- Requirement Coverage issue section
- Tests project report
- Test Sets project report
- Test Plan issue section
Hence let's say you have a set of Tests that need to be executed in both IOS and Android environments. You can now see the status for a specific environment only.
Built-in Test Case Importer
Now, with the new built-in Test Case Importer you can import manual Tests from a human readable CSV source file, without needing to use an external tool in your computer.
With the Test Case Importer you just need the CSV containing the manual test steps and your JIRA instance.
Importing your manual Tests from other tools has never been easier.
Learn more here.
Integration with Structure add-on
If you have Structure add-on you will be able to see and manage the relation between Tests and the Test Sets, Test Execution or Test Plans issues.
The Xray extender allows you to simply drag Xray issues into your "structure" and will automatically show you the Tests that are associated with them.
If you drag a Test into an issue of those types it will be associated with it and the same happens with a Test Set. If you drag a Test Set into an issue, all the Tests in the Test Set will be added to the issue. And of course, if you remove a Test from an issue its association will also be removed.
Learn more here.
Merge Test Specification changes into existing Test Runs
Xray assures data consistency, making sure your previous/existing Test Runs are not changed without your consent. Each Test Run contains a copy of the original Test specification.
However, sometimes you may need to update the specification of a Test Run with the current one of the Test, perhaps to fix some typo or clarify some point.
Now you can choose if you want to update the specifications of your existing Test Runs, without losing the already reported results.
Import existing Cucumber Tests into Xray using the REST API
Now you can migrate your legacy Cucumber projects and start managing them in Xray.
A new REST API endpoint will make it possible to import Cucumber Scenario and Scenario Outlines from existing Cucumber .feature files.
Learn more here.
And much more...
Xray issues improvements | Execution Screen | JQL functions |
---|---|---|
Tests
Manual Tests
Test Plan
Test Sets
|
|
|
New Features and Bug Fixes in this release