Date: Fri, 29 Mar 2024 09:40:28 +0000 (UTC) Message-ID: <1683539020.11282.1711705228086@docs.getxray.app> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11281_1260776885.1711705228086" ------=_Part_11281_1260776885.1711705228086 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Xray provides powerful capabilities for analysis of test results and cov= erage on a per environment basis, allowing users to easily understand how t= ests and requirements are on specific target environments.
However, Xray is somehow limited on the management capabilites of = Test Environments; they are created similar to labels and they're available= to all your Jira projects. You may require more advanced management c= apabilities for your Test Environments. Fortunately, there is Apwide Golive (previously known as "Apwide Test Environment Manage= r") which complements Xray built-in features, allowing you to fully manage = Test Environments, their availability amongst other.
On Xray screens, the QA team knows as soon as an Environment becomes uns= table or when the wrong version of an application is deployed. Efficiency i= ncreases with clickable links to access the Environments and the possibilit= y to book dedicated Environments for test campaigns.
Test Executions and Test Plans are now planned on a Timeline with drag-a= nd-drop and Xray issues dates are automatically updated. Jira filters can b= e 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 environ= ment status. You can also easily understand how tests and requirements are = faring on specific target environments.
Apwide Golive is a complete Test Environments management solution.<= /p>
A Test Environment is composed by the definition of an "application" and= a "category".
An "application" is an abstraction of some generic application entity; i= t's not exactly a "JIRA project", although it may be bound to the vers= ions of some given project. An environment "category" defines the purpose o= f the Test Environment. More information on the core concepts here.
Some of Apwide Golive features include:
Please note
If you have further questions concerning Apwide Golive app, please conta= ct their team here.
The current integration with Xray all= ows you to:
As limitations, please consider that:
In order to use the new extenders that Xray provides, you need to:=
Learn more
Please see the installation tutorial in video below.
The configuration is managed in "Apwide Xray-Integration" app settings.<= /p>
The integration needs to be explicitly enabled; it's also possible to en= force the usage of Apwide only based Test Environments.
Whenever creating a Test Execution, or whenever editing an existing one,= you can specify a Test Environment being managed by Apwide Golive.
Depending on the Apwide Xray-Integration configuration, you may be limit= ed or not to use just Test Environments from Apwide.
It's possible to display current/actual information abo= ut a given Test Environment in different places.
1. In Test Execution issue screen
2. In the Test Runs section, in the Test = issue screen
3. In the reports
Test Executions can be planned right in the Timeline view provided by Ap= wide Golive.
2. Define the name and the colour corresp= onding of the issues
3. Specify the JQL to define the scope fo= r the issues
4."Def= ine the Default Values that will be pre-filled so that new Test Executions = can be created using the calendar drag-and-drop (refer to the below video)<= span class=3D"confluence-embedded-file-wrapper confluence-embedded-manual-s= ize">
4. You can now see the Test Executions is= sues in the Timeline; you can also change the planning dates by moving the = left/right side edges of the issue item
Please note
It's also possible to manage Test Plans planning dates using this app, a= s long as you also include the Test Environments custom field in the screen= s associated with Test Plan issues.
You need to update the "Test Environments" custom field in Jira's "Custo= m Fields" administration section, so that the applicable contexts will also= include the Test Plan issue type.