Page History
...
Ranorex can be seen as a keyword-driven framework for implementing GUI test automation across a broad set of technologies, including desktop, web, and mobile. It's a codeless test automation solutiion. Ranorex provides comprehensive support for test automation as detailed in its core features. Data-driven testing is also supported.
Ranorex provides Ranorex Studio, the main application to implement and organize automated test scripts. Ranorex Studio has multiple components, including a recorder (Ranorex Recorder) and a object/element identifier (Ranorex Spy).
In this article we'll highlight some of Ranorex core concepts and see how to have visilbity of test automation results in Jira, using Xray.
Ranorex concepts
| Ranorex concept | Description | |
|---|---|---|
| Solution | In Ranorex Studio, a solution is the top-level container that contains all other test files. Solutions are organized into one or more projects. Whenever creating a solution, we may identify the type of application we aim to test (e.g. desktop, web, mobile). A solution has always a "test suite" project. | |
| Project | A tailored place to organize test files. A project can be of one of several types, including "test suite", which offer different capabilities. | |
| Test suite | The test suite is where you build, organize, and run your tests in Ranorex Studio. A test suite consists primarily of test cases. | |
| Test case | A test, composed of Modules, which in turn are composed of Actions. | |
| Module | Modules can be reused between Test cases. | |
| Action | A step, inside a Module. Can be an action a mouse/keyboard interaction or a validation. | |
| Validation | An assertion, a validation. | |
| Repository | A Repository contains Repository Items (i.e. UI elements) organized in a tree-like structure. UI elements that contain other UI elements are represented as folders in the repository, with app folders acting as top-level elements and rooted folders as children. | |
| Repository item | A representation of a user interface (UI) element used in a test. Each repository item has a name and is defined by its RanoreXPath (i.e. path). |
...
For that, we choose "Validate" and move the mouse hover the element we want to validate and click on it.
A validation can have dialog enable us to perform multiple asserts at the same time, on a given element (e.g. element exists, is visible, contains a given text). Each assert/validation will be created as a "Validate" action in our module.
A possible "Valid Login" test case could be composed of a setup section to open the browser (i.e. using the "OpenBrowser" module), a recorded module where we enter the credentials and validate the welcome page, followed by the close browser instruction (as part of the CloseBrowser module).
The "Login_with_valid_credentials" module could be composed of these actions, depending on the actions you make or wish to make.
Integrating with Xray to have visibility of testing results in Jira
...
If we run the tests from within the Ranorex Studio UI, we can go to the properties of our test suite to customize the report file name, the reports directory, and enable the JUnit XML report.
If we run the tests from the command-line, by calling the executable built by Ranorex, we can enable the JUnit XML report, customize the report file base file name, among other options.
...