Page History
...
Any additional imports of results, will appear automatically reflected on the user story issue screen as the Tests are already linked to the user story.
Run iterations and data-driven tests
Ranorex Studio has support for run iterations and data-driven tests.
These are two different concepts; while run interations are just a way to run the same test case multiple times by executing the exact same modules and actions, data-driven tests will impact on the action being performed (e.g. for exercising the same test case but with different inputs).
It's possible to have visibility of the correspoding test results in Jira using Xray but some.
| Note | ||
|---|---|---|
| ||
Due to the way Ranorex Studio reports these results on the JUnit XML report, different Test issues will be created for each run iteration or data row. We should have this in mind as it hardens management of these Test issues (e.g. number of unrelated Tests, linkage to user stories). |
Run iterations
On the properties of a test case, we can configure the number of run iterations (i.e. iteration count).
After running the test case and importing the results to Xray using the JUnit XML report, a Test Execution with 3 Tests is created in Xray.
Due to the way run iterations are reported in the JUnit XML report, each run iteration for our test case is abstracted as a different Test issue, with the run iteration being part of its defintion.
In other words, we'll have as many Test issues as the iteration count configured for the test case.
Data-driven tests
To make a data-driven test we need to use some variables in our actions, instead of using hardcoded values/strings.
Then we need to configure a data-source for the selected test case.
There are different types of data-sources; a simple built-in data table can be used to specify several named columns and some rows of data for them.
We then need to bind the columns of our data-source to the variables used in the previous module.
We can run the test case in Ranorex Studio and see the results for each data row.
After running the test case and importing the results to Xray using the JUnit XML report, a Test Execution having 3 Tests related to our data-source is created in Xray.
Due to the way run iterations are reported in the JUnit XML report, each run iteration for our test case is abstracted as a different Test issue, with the run iteration being part of its defintion.
In other words, we'll have as many Test issues as the iteration count configured for the test case.
References
- Ranorex web site
- Ranorex User Guide
- Integrating Ranorex with Jenkins
...