Page History
...
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 and mapping to Xra
| Ranorex concept | Description | Xray concept |
|---|---|---|
| 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. | Doesn't exist as an entity. Will be visible and part of the definition of each Test issue. |
| Test case | A test, composed of Modules, which in turn are composed of Actions. | Test issue. |
| Module | Modules can be reused between Test cases. | |
| Action | A step, inside a Module. Can be 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). |
| Overall test status | yes | |
Actions | no | |
| Videos | no | perhaps |
| Data-driven | ||
...
We will implement some automated tests for a dummy web site, providing an authentication mechanism that we aim to check, namelly the login and logout features.
Our tests, part of a test suite, include:
...