Overview
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 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).
| 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 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 | ||
How to
We will implement some automated tests for a dummy web site, providing an authentication mechanism that we aim to check.
Our tests, part of a test suite, include:
- valid login
- invalid login
- valid logout
- invalid login (data-driven scenario)
We star byt creating a solution, web-based as we aim to test a web site.
References
- Ranorex web site
- Ranorex User Guide
- Integrating Ranorex with Jenkins