Date: Fri, 29 Mar 2024 02:28:32 +0000 (UTC) Message-ID: <975174118.10892.1711679312111@docs.getxray.app> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10891_1818584539.1711679312095" ------=_Part_10891_1818584539.1711679312095 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
May 29, 2021
The Xray team is proud to announce the release of Xray Clou=
d 1.1.56-2.000.000. This version's major features include importing screenshots from Robot Framework, grouping defects and=
evidence on the overall panel within the execution screen, and an=
overall UI/UX revamp of the Xray issue panels and executi=
on page.
Test parameterization is a powerfu= l practice that allows the same test to be executed multiple times with dif= ferent parameters. Parameters are similar to input values (variables) that = can change with each execution.
Parameterized tests in Xray are defined just like any other test with th= e addition of some parameter names within the specification usin= g the following notation: ${PARAMETER_NAME}. This notation is used to reference parameters within the test steps.
Precondition = ;issues can also be parameteri= zed by including parameter names in the precondition specification.<= /p>
The parameters, along with their values, are defined within a = ;dataset. A dataset is a collection of data represe= nted with a tabular view where every column of the table represents a parti= cular variable (or parameter), and each = row corresponds to a given record (or iteration= strong>) of the dataset. The number of rows in the dataset determines the n= umber of iterations to execute.
A dataset can be defined in the following entities/scopes:
The closest dataset to the test run will be the one used to generate the= iterations, effectively overriding any dataset defined in higher levels.= p>
All iterations for a given test ar= e executed within the context of the same test run. Each iteration can be e= xpanded, and the steps executed individually. The step parameters will be r= eplaced by the corresponding iteration values. The steps affect the iterati= on status, which in turn affects the overall test run status.
Learn more here.
When executing Robot Framework tests, we can capture screenshots after e= xecuting certain steps and include them in the execution report.
These screenshots will now be imported by Xray and will be provided on t= he execution screen as evidence of the execution.
Learn more about this feature here.
We have redesigned some screens and issue panels in Xray.
Xray issue panels (e.g. Test issue) are now organized in tabs. This can = effectively reduce page load times when navigating to Xray issues as there = is now a single central panel.
The execution page has been improved also. It now features a "findings" = section grouping the defects, evidence, and comments sections. This section= is collapsed when there are no artefacts (defects, evidence, or comments) = focusing the user on what's most important (the test details section) in or= der to execute the test.
It is now possible to aggregate all defects and evidence on the overall = top panel within the execution screen. This way, both the global defects an= d the defects associated with steps will be shown on the same panel, making= it easier to view all the defects created during execution. The same is al= so true with evidence.
This feature is optional and you can disable it within the execution scr= een.
Find out more about this feature here= a>.
=
Documentation is always important and sometimes you may miss it.
Check out these articles that we've recently added to our extensive docume=
ntation.
Features and Bug Fixes in this release