Integrating Ranorex with Testlink and Jenkins

Posted by Roland Enzinger on Thursday, March 5th, 2015

This blog post is heavily based on ideas and instructions provided by Timm Groeger from Buhl Data GmbH.

Testlink Jenkins Integration with Ranorex Automated Test Software

Testlink is a very powerful test management tool which is web based and open source. In addition to support for test cases, test suites, test plans and test projects, it also supports management for feature requirements and test specifications. Furthermore, an interface for defect/issue management (e.g. Jira, Bugzilla, Mantis, etc.) exists in the framework of TestLink. Test cases can be marked as manual or automated.

Following the instructions below allows you to incorporate test management with automated test execution controlled by a CI tool (e.g. Jenkins) and executed by Ranorex. Afterwards the test results will be provided for the test management tool. This seamless integration allows traceability from beginning to end – i.e. from setting the requirements to all assigned test cases, including their (automated) test results and reports.

Read more »

Automated Regression Testing with Ranorex

Posted by Tobias Walter on Thursday, January 15th, 2015

This blog post will explain the term regression testing and how Ranorex test automation can support in doing functional regression testing. Additionally the blog post will confront you with the problem occurring with regression testing including a strategy to overcome it.


Read more »

Integrating Ranorex Test Cases into Jira

Posted by Christian Breitwieser on Wednesday, November 26th, 2014

Jira is an issue and project tracing software from Atlassian. The following article describes integrating Ranorex Test Cases into Jira. That way you will empower Ranorex to submit or modify testing issues within Jira in an automated way.


As Jira offers a REST web service (API description available here), it becomes possible to submit issues automatically. This is achieved using the JiraRestClient  and RestSharp.

These libraries are wrapped with Ranorex functionality, forming re-usable modules, available within this library. The integration of these Jira testing modules into Ranorex Test Automation is described subsequently.
Read more »

Create and Share your own Custom Actions for the Recorder

Posted by Roland Enzinger on Thursday, November 6th, 2014

This article explains how custom actions can be implemented and used directly within Ranorex Recorder. Additionally, it provides an example implementation of a custom (user code) action. It furthermore describes how this action can easily be shared – e.g. to also make such actions available for non-programmers, mainly through the use of Ranorex Recorder.


Read more »

Integrate Ranorex Tests in andagon’s ALM tool aqua

Posted by Guest Blogger on Wednesday, October 29th, 2014

Guest blog post by Stefan Büssemaker, Innovation Manager at andagon GmbH

This blog post will illustrate the interaction between Ranorex and the application lifecycle management solution aqua.

In a few simple steps you can expand your Ranorex test cases with the powerful ALM tool aqua.

Read more »

Sharing Data from One Ranorex Module to Another

Posted by Corinna Kindlhofer on Tuesday, July 29th, 2014

Sometimes it is necessary to access the value of a specific variable in more than only one module in a test case.

An example for this would be any kind of converter: In one module the value to be converted is read in. In another module this value is converted. Needless to say, in the converting module the value from the previous module should be used.

This blog post will show how to do this step-by-step.

Read more »

Fully integrate your Ranorex Report with CI tools like Jenkins using xUnit

Posted by Roland Enzinger on Tuesday, April 15th, 2014

A Ranorex test automation project creates an executable file which returns a two-state test result indicating a success or a failure. Continuous Integration (CI) tools like Jenkins, Hudson, TeamCity, CruiseControl, Bamboo etc. are able to call automated tests and do understand these two-state test results. This is similar with ALM tools like Polarion or Jira. In short, in the world of CI and ALM, test automation results are reflected by a single flag, success or failure.

This blog describes how a Ranorex Report can be automatically transformed into xUnit format by using an XSL Transformation (XSLT). This transformation allows the CI tool to fully understand the result of each test case, not only whether the entire test run passed or failed.

Read more »

How to Test Web Services with Ranorex

Posted by Tobias Walter on Tuesday, January 21st, 2014

This blog post will illustrate how easy it is to test your web service using Ranorex. In detail you will add a web reference of your web service to your Ranorex Solution and validate the functionality of the service via user code actions.

Test Web Services With Ranorex

To illustrate web service testing, we have chosen an easy to follow example based on sample web service provided by Basically we will take a given temperature in Celsius, convert it to Fahrenheit and reconvert it back to Celsius. Finally we compare the calculated value with the initial one.
Read more »

Making Use of the Search Engine!

Posted by Tobias Walter on Thursday, October 17th, 2013

The Ranorex website contains an amazing collection of test automation knowledge. First off, there’s our online user guide where you can find a walk-through explanation of all the Ranorex Tools and Features. There’s also the forum which includes a colorful mix of useful hints and highly specialized and detailed technical knowledge posted by our own Ranorex Experts as well as by the community. Lastly, of course there are also many useful how-tos and articles in the blog section.

Knowledge Base

All these resources mean that you can pick specific user guide sections that you are interested in, have a look at the latest forum posts or choose a specific article from our blog archive – you’re sure to find what you are looking for!
Read more »

Keyword-Driven Test Automation Framework

Posted by Tobias Walter on Thursday, June 13th, 2013

The basic idea behind the keyword-driven testing approach in test automation is to separate the automation from the test case design. This is usually achieved by using an additional layer of abstraction where the tests itself are defined technology-independent and readable for non-technical personnel as well. Thus, a keyword could be defined as a set of actions performing a “Login” or “Save”-Operation.

Based on the technology-independency, tests might be developed earlier in the QA process and beneficially they are easier to maintain for that reason. Next to that, labor can be divided easier based on different levels of technical experience. Here the automation (keyword implementation) can be done by technically experienced team members whereas the test case design (keyword usage) can be done by domain testers who don’t need to have technical skills to that extent.

Keyword Driven Test Automation Framework

This blog post describes how the keyword driven testing approach in test automation can be followed within Ranorex, granulated on two different levels.

Read more »