Date: Fri, 29 Mar 2024 08:04:08 +0000 (UTC) Message-ID: <23961712.11178.1711699448981@docs.getxray.app> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11177_69549899.1711699448979" ------=_Part_11177_69549899.1711699448979 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
2nd August 2017= span>
The Xray for JIRA team announces the release of Xray 2.3.0<= /strong>. Version 2.3 contains new features as well as bug fixes. Please ch= eck the highlights below.
This report shows a list of Test Runs with detailed info for each one, i= ncluding related Test, Test Execution and Test Plan entities, execution dat= es, linked defects among other.
Some possible usage scenarios:
Learn more here.
The Test Runs List gadget will provide the ability to include Test Runs in= your JIRA dashboards and in your Confluence pages. Thus, listing all the T= est Runs of a given Test Execution or the ones assigned to/executed by a gi= ven user will be straightforward.
Learn more here.
Day after day, people come from legacy tools and want to use Xray straig= htaway in order to improve their QA. We know that test cases normally have = one or more attachments that complement the specification of each test.
To simplify the migration to JIRA and to Xray, the built-in Test Cas= e Importer now supports adding attachments both at step level and = globally at Test level. Attachments may be imported locally from a JIRA ser= ver folder=E2=80=99s directory or from remote URLs.
One or more attachments may be specified and this can be done either at = the Test level, in the Test=E2=80=99s first row, or at the step level in th= e subsequent rows.
Learn more here.
For new Cucumber imported results, you will be able to see= attachments in-context, at step level. This applies also to Cucumber hooks= .
We understand that you may need to= extract and process your reports further.
Therefore, we=E2=80=99re making th= e Test Runs, Test Executions and Test Plans reports available as CSV via an= Export action.
The Test Plan tracks a group of Tests in a given version. However,= you may want to know what requirements are being covered by the Tests that= are part of a given Test Plan, in order to answer the question =E2=80=9CWh= at requirements am I validating?=E2=80=9D. The testPlanRequi= rements() JQL function provides exactly that, for one give= n Test Plan issue key or for a list of Test Plans, by specifying a saved fi= lter as argument.
Likewise, the requirementTests() functio= n was improved to support a saved filter as argument. Thus, you can now eas= ily obtain all the Tests that cover a certain group of requirements.
The new testPlanTestExecutions() functio= n provides all the Test Executions for a given Test Plan issue key.
Learn more about the new JQL function= s here.