Page History
...
This will be used to implement interactions with our web site, without having to code.
We choose "Record" adn then we're redirected to the browser, where we can perform actions which will be recorded.
While recording the actions of our module, we can remove some that may be added by accident for example. We can also pause and stop recording.
In order to implement a test, we need to add at least one validation.
For that, we choose "Validate" and move the mouse hover the element we want to validate and click on it.
A validation can have perform multiple asserts at the same time, on a given element (e.g. element exists, is visible, contains a given text).
Integrating with Xray to have visibility of testing results in Jira
...
After uploading the test automation results, users can link the Test issues to existing user stories or requirements. That will enable users to track coverage and thus assess if user stories are covered by automated test scripts and if based on that, the corresponding user story can be considered to OK or NOK.
| 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, we can then link it to the Tests that correspond to the Test Cases implemented using Ranorex.
References
- Ranorex web site
- Ranorex User Guide
- Integrating Ranorex with Jenkins