Page History
...
A Test issue will be auto-provisioned, unless it already exists, per each Test Case.
The Test Suite name along with the Test Case name will be used as unique identifier for the Generic Test that will be created.
In the Test Run details of the corresponding Test in Xray, we can see this information along with the overall result. The original Test Suite name appears also as a context.
Tips
Seeing the impacts of test automation results on user stories or requirements
...
| Info |
|---|
| Please remember that coverage is an heuristic but that can still be quite helpful to assess the readiness of user stories, individually or at the release level. |
Assuming we already have a user story (new or existing), we can then link it to the Tests that correspond to the Test Cases implemented using Ranorex.
We can do that right from the user story issue screen, using the "Link" action.
Then, we select the Tests that were auto-provisioned earlier on upon the first import of the test report.
Finally, we can see the latest test results right from the user story issue screen along with the calculated coverage information for the user story; the latter is avaiable (both on the Requirement Status custom field and also on the Test Coverage panel.
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.
References
- Ranorex web site
- Ranorex User Guide
- Integrating Ranorex with Jenkins
...