Ranorex Studio Reviews

Cross browser testing and the ability to perform mobile test automation. Due to this, you do not need to buy two different solutions for mobile and web channels separately.

Our core banking application is developed as a plugin of Chrome. Most of the automation tools do not work properly on Chrome, but Ranorex provides this with less maintenance costs. Also, the automation platform is useful for us.

I encountered a problem during div element recognition. This point could be enhanced.

I've used it for three years.

No issues encountered.

No issues encountered.

No issues encountered.

9/10

9/10

I had experience on QTP and RFT. They do not support the latest version of browsers or mobile environments. Their costs are high, accordingly.

It was simple.

We implemented it in-house.

It is simple and stable solution.

Ranorex Recorder records and replays keyboard and mouse actions performed by the user.

I've used it for one year.

Yes, however many issues were in-house. Those that were not, were typically dealt with expediently with an update or offered support.

Yes, however many issues were in-house. Those that were not, were typically dealt with expediently with an update or offered support.

It's above average.

It was pretty straightforward.

We performed implementation in-house. The difficulty of implementation can scale with the size and complexity of your software project, it can become quite a daunting task.

My advice is that you back up and test your current project in a separate environment. Start small, and dedicate time to learning the different Ranorex tools and features.

The returns will always vary depending on the software. It is a great tool for some shops to start out new developers on, helping them learn more about the integral parts of a system. It can be worth it as a learning aid or knowledge base alone.

This is completely based on the project, and a company's willingness to forgo other cheaper alternatives. Ranorex does offer a free trial which should give most customers an idea of what they're getting into.

We tried several, and we chose Ranorex for it’s ability to cover large amounts of testing with minimal coding.

As a stand alone product Ranorex is quite useful. However, if you plan to implement and merge this with a project that is complex, it requires full automation, API integration, and has a large data set it can be arduous.

Our team highly appreciates the ability to use the Ranorex library directly in code. That has enabled to create our own libraries (we call them adaptors) which access various parts of our product.

Due to the ability to code our own adaptors, the code maintenance effort has been reduced. We do not use the Ranorex Studio thus there is no “spaghetti code”, which is difficult to maintain, being created.

Ranorex has truly been a “little monster” able to access even the most complex custom WPF controls. It is a pity Ranorex is not engaging model-based testing technologies.

We have been using the product for the past four years and are quite satisfied with its performance.

No issues encountered.

No issues encountered.

No issues encountered.

In the rare cases where we have had to contact the technical support, the reply via email came relatively quickly.

All we had to do is to link a couple of .dlls into the automation solution. The complexity was in how to structure the adaptors so that the code maintenance effort could be kept as low as possible, but that had got nothing to do with Ranorex.

We are a QA team capable of writing automation code, thus we implemented everything in-house. Before implementation, think hard on how to structure your automation code, especially your adaptors.

We have a number of floating licenses.

We initially tried out the CodedUI by Microsoft, but the coding effort plus the product maturity at that stage convinced us to pick Ranorex.

We have been employing Ranorex in the field of desktop PC application UI automation. In this particular area Ranorex proved to be a perfect choice. Unfortunately we could not gather any experience in the field of web application automation.

The most useful features to me are the ability to write test scripts in C#, and also record/playback any and all test steps. Ranorex Spy is also a very useful tool.

Ranorex has significantly cut down the time it takes me to run through multiple, repetitive test steps.

They should have support for other OS’s, aside from only supporting Windows. It would also be great if they supported JavaScript as a usable language to write code modules in.

I’ve been using Ranorex for about five to six months.

Ranorex’s customer service is outstanding.

When something is out, I immediately email their tech support and will usually hear back from them within an hour. The forums are also very helpful.

Setting up Ranorex and jumping into your first test suite is extremely easy, even for non-programmers The record/playback feature makes it easy for anyone to automate a test case..

The best advice I can give is geared towards implementation. If you’re capable of writing your own test scripts, then I wouldn’t suggest using the Record/Playback feature at all, aside from maybe looking at the generated code module for help on starting a new test case. There are a lot more constraints that come with using the record/playback method, and you cannot easily implement conditional statements or parameters, like you would be able to in the code modules.

Started with recording and playback and data-driven, later on we used the API with code module.

It's easy to use the test suite and add test cases to do our product bug fixes, and software pre-release regression tests, and continuous Integration testing with Jenkins CI tool for each software build test.

It needs a more robust capture & replay, and the GUI object recognition needs improvement too. Mobile device testing should not only bbe limited to phones and tablets, I would like to see if it can support user devices such as printers like Ricoh, Xerox, and Konica and their emulators.

I've used it for around three years.

So far so good.

So far so good.

So far so good.

8/10

8/10

We tried QTP many years ago, which was good but expensive. Also, Selenium is limited to browser and mobile, and does not support desktop app.

It very straightforward. So good, and easy.

The license types can be confusing.

The mobile testing feature is the most valuable feature for me.

I have been able to run specific tests on different platforms and browsers.

The compatibility with different browsers needs to be improved.

I've used it for three to six months.

There were issues with objects identification.

9/10.

9/10.

I tried to use different products Selenium, TestComplete, amongst others, but this was very familiar, fast, adaptable and flexible.

It was simple. Everything was inline, but some features needed support – like creating virtual platforms for testing. Connecting to a real IOS was impossible without a dev account.

In my company, the project is a desktop application. We are using Ranorex to record the test cases.

It has reduced the cost of production and operations. It has reduced the cost of QA in my company and reduced the human resources needed. And the tool is very easy to use.

Regression testing is very important for our company, as is the continuous integration process.

Binding to other sources is very good but the object recognition in .NET desktop applications often doesn't work. 

Ranorex is used in Windows while other solutions, for example, Katalon Studio, are cross-platform. (But in my opinion, overall, Ranorex is better).

When Ranorex is upgraded, the compatibility with other projects, in version control, in-house or on-premise, fails on occasion. However, overall, the stability is good.

Scalability with Ranorex is a problem. The way to scale is to buy more licenses.

The support for Ranorex is very good and fast. User requests are answered quickly.

We knew we needed a new solution because testing was only executed manually. A better approach for the team was to automate testing to reduce costs.

When selecting a vendor, the most important criteria are support, providing a trial version for testing the tool, and the functionality the tool offers.

The setup is easy.

HPE, and Selenium WebDriver, which is open-source. We went with Ranorex because of compliance and the company's requirements.

I would rate this solution an eight out of 10 because of the expense of licenses and lack of simultaneous execution. It's limited to only one machine or computer.

My advice is to compare solutions. Two years ago there were very different options in the market. Compare Katalon Studios with Ranorex.