Versions Compared

Old Version 5

changes.mady.by.user Bruno Conde

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Conde

Saved on

Key

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

...

Expand
titleParameterized Tests and data driven testing
Panel

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.


Image RemovedImage Added


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 that, in turn, affects the overall test run status.

Image RemovedImage Added


Learn more about parameterized tests here.

In the works

...

titleUpdated Xray connector app for Bamboo

...

borderColor#EAECEE
borderWidth1px
borderStylesolid

...


Expand
titleModular Tests
Panel
borderColor#EAECEE
borderWidth1px
borderStylesolid

Ability to call an existing Test from the step of another Test and thus use tests as reusable building blocks for the composition of more complex testing scenarios.

The called test can be executed independently or be used as a step of a broader test (e.g. "login as the admin user").

Future Versions


Expand
titleTest Parameterization
Panel
borderColor#EAECEE
borderWidth1px
borderStylesolid

Ability to define variables in the Test specification (e.g. the steps) that can be replaced by values inherited from different sources (a calling test for example). In that scenario, the called test is used as a parameterized template (e.g. "login as the specified user").

Expand
titleData-driven testing
Updated Xray connector app for Bamboo
Panel
borderColor#EAECEE
borderWidth1px
borderStylesolid

Ability to perform data-driven testing (i.e. execute the same test against multiple parameters, for different combinations of data).

Data-driven testing will be implemented using the foundations of test parameterization.

Data may be defined at multiple levels including:

  • the test level (default values)
  • the caller test
  • the Test Plan
  • the Test Execution

Data might also be imported from external sources (like CSV files).

...

The Xray Connector app for Bamboo will be updated in order to support new functionality and APIs already available in Xray. The Xray Connector will also support Xray cloud APIs and connectivity.

Expand
titleSupport Jira Issue Archiving
Panel
borderColor#EAECEE
borderWidth1px
borderStylesolid

Jira Datacenter supports archiving of issues and projects since v8.1. By archiving issues, Jira will remove them from the indexes. The archived issues will still be accessible in read-only mode, however, they will not appear in Jira searches. This enhances Jira performance because Jira stores less data.

The goal of this feature is to support issue archiving so that Xray issues can be archived without some of the undesirable side effects (described here). A good use case for archiving Xray issues is to archive old Test Executions, especially if continuous integration processes are used. These can quickly create many Test Execution issues while importing new execution results into Xray on a daily basis. These issues are good candidates to be archived.

...