Versions Compared

Old Version 10

changes.mady.by.user Bruno Conde

Saved on

compared with

New Version 11

changes.mady.by.user Bruno Conde

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
Column
width

...

Parameterized tests (smile)

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.

Precondition issues can also be parameterized by including parameter names in the precondition specification.

The parameters, along with their values, are defined within a dataset. 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:

  1. Test (default dataset)
  2. Test Plan - Test
  3. 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.

Learn more here.

...

width60%
Section
Column
width80%

2 July 2021

The Xray team is proud to announce the release of Xray 5.0.

This version's major features include parameterized tests,  data-driven testing,  support for Robot Framework v4.0, and grouping defects and evidence evidence on the overall panel within the execution screen.

Column
width20%

...

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
Column
width40%

Parameterized tests (smile)


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 the test steps.

Precondition  issues can also be parameterized by including parameter names in the precondition specification.

The parameters, along with their values, are defined within a  dataset. A dataset is a collection of data represented with a tabular view where every column of the table represents a particular variable (or or parameter), and each row corresponds to a given record (or 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:

  1. Test (default dataset)
  2. Test Plan - Test
  3. 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.


Learn more here.

Column
width60%


Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

Group defects and evidence on the execution screen

Column
width70%


Column
width30%

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.


Find out more about this feature feature here.

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section
Column
width40%

Search Test Steps


(...)


Learn more more here.

Column
width60%


Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

Support for Robot Framework 4.0

Column
width70%


Column
width30%


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.


Find out more about this feature here.

...