You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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 on the overall panel within the execution screen.

Upgrade Notes

Downgrading from Xray 5.x.x


Downgrading from Xray 5.x.x to a previous version will have the following side-effects on Test Runs with dataset:

  • Test parameters will no longer be converted on the Test Run page, this includes Test Step definitions and Pre-Conditions;
  • When loading a Test Run created on version 5.x.x, the merge/reset message will be displayed;
  • When merging a Test Run created on version 5.x.x with the new Test Step definition, all Test Step results will be updated but the reset/merge message will still be displayed;
  • A Test Run created on version 5.x.x with iterations will be displayed in a "flat mode". The iterations will no longer be available and all the Test Step results from each iteration will be presented on the Test Steps section;
  • After the downgrade, the integrity checker will fail on "Check for invalid Mementos" for all Test Runs created on version 5.x.x. We recommend running the integrity checker before downgrading to get rid of possible invalid mementos.


Release highlights 


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.


Group defects and evidence on the execution screen


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.

Search Test Steps


(...)


Learn more here.


Support for Robot Framework 4.0



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.

Just one more, yet important, thing...


Documentation is always important and sometimes you may miss it. We added a set of relevant articles to our already extensive documentation.

In this release, you may find new articles to facilitate integration with well-known CI/CD tools, including Travis CI and GitHub. We added also tutorials for Playwright, Cypress, WebdriverIO with corresponding open-source repositories, so you can easily try out those frameworks and integrate with Xray to have visibility of test automation results. You may find the code for these tutorials, and more, in our GitHub account. Check them out and let us know your feedback (smile) 

A new section was created for Model-Based testing along with some tutorials.

Here's a sum-up of all the relevant articles that we've added and updated recently:




All New Features and Bug Fixes in this release

 

Key Summary T Created P Status Resolution
Refresh


  • No labels