Test parameterization is a powerful practice that allows the same test to be executed multiple times with different 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 the addition of some parameter names within the specification using the following notation: ${PARAMETER_NAME}. This notation is used to reference parameters within the test steps.
Preconditionissues can also be parameterized by including parameter names in the precondition specification.
The parameters, along with their values, are defined within adataset. A dataset is a collection of data represented with a tabular view where every column of the table represents a particular variable (or parameter), and each row corresponds to a given record (or iteration) of the dataset. The number of rows in the dataset determines the number of iterations to execute.
A dataset can be defined in the following entities/scopes:
Test (default dataset)
Test Plan - Test
Test Execution - Test (Test Run)
The closest dataset to the test run will be the one used to generate the iterations, effectively overriding any dataset defined in higher levels.
All iterations for a given test are executed within the context of the same test run. Each iteration can be expanded, and the steps executed individually. The step parameters will be replaced by the corresponding iteration values. The steps affect the iteration status, which in turn affects the overall test run status.
Group defects and evidence on the execution screen
Column
width
70%
Image Added
Column
width
30%
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 and 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 also true with evidence.
This feature is optional and you can disable it within the execution screen.
Searching for text within Test Steps of a manual Test case is now easier with the addition of a dedicated search field.
The browser search might not be a good solution because not all the steps are loaded at a given time due to performance reasons. Also, the steps might be collapsed.
Therefore, we have now included this search field that allows you to search in all Test Steps. This includes all Xray native fields (e.g. Action, Data, Expected Result) and also Test Step custom fields.
Robot Framework 4.0 is a new major release with a lot of big new features such as the SKIP status and native IF/ELSE support as well as enhancements to, for example, type conversion and Libdoc.
These changes have not been possible without breaking backward compatibility in some cases.
Xray now supports the new Robot Framework 4.0 report format.
