Ranorex Studio Reviews

We primarily use the libraries provided by Ranorex to access our application, and the Ranorex Spy, to view the current application's object model.

By using this product, we have been able to explore some more advanced strategies in developing our automation which has been able to carry over to other automation teams. This has made all of our automation teams suites more robust and accurate with their testing.

There is too much focus on the drag-and-drop features of Ranorex, and not enough focus on the coding modules which we use extensively. As a programmer, would like to be able to come up with a code only interface so that features such as the Test Suite don't have to be used if they don't want to be.

I've used it for around two years.

For a very long time, we were running into crashes with either Ranorex or Ranorex's utility (UIALauncher) which would stop our testing dead in its tracks. These areas would then need to be run test by test, and not in whole batches at a time. We eventually tracked the issue down ourselves to be a rare condition between Ranorex and Windows 8, where both systems were trying to access an element at the same time, and was failing.

Other then not being able to track down the issue above that was plaguing us for quite some time, the Ranorex customer support has been great. The only complaint would be that at one time, we were having issues with our licensing, and while one of our engineers was talking to them for a while. All of a sudden, they said that they were required only the primary account holder to talk to them, which needlessly required a third party to get involved in what was a very minor issue.

When we started evaluating Ranorex, we were already using a number of other products for the various platforms we run automaiton against. Unfortunately, none of the products we were using at the time had the capability to automate Windows 8 apps. Ranorex's ability to do this (the only product we found at the time that could) is the reason we chose the product.

Setup and installation of Ranorex was extremely straightforward. However, getting the initial script running was a bit complex, as we soon found that parts of our application weren't accessible through Ranorex, and the way Ranorex wanted us to create scripts wasn't intuitive to us. We eventually opted out of "their way" of doing things, which is more for a non-coding QA person, and opted for a 99% programming method.

All implementation is done in house with a small team of three to four engineers. My best advice for implementation is that if you can, try to go through a pure programming route with your implementation, and not through the recorded modules. While it may be more time investment in the beginning, it will pay off in the end because you will have a more robust suite that will scale much better then using the "standard" Ranorex Route.

Ranorex, like many other automation tools is expensive. I highly suggest planning out how many licenses you need ahead of time, and try to plan your suite to use as many licenses as possible. With this approach you should be able to get as much testing done as possible without breaking the bank with licensing costs.

• Spy
• CodeModule
• XPath

Automation coverage overnight is very useful. Compared to Selenium, Ranorex has a very small learning curve, so most of the technical QA people can start development with it right away.

They need to have modularity (running concurrently different parts of the tests on different environments and reporting back to centralized run centre). Currently we are implementing this functionality via code, but feature should give a lot of advantages.

I've used it for three years.

The scalability is limited to one process. You cannot have multiple reports combined together automatically, because each run is independent.

The support is pretty good, they have been able to work out some bugs with their licensing and they seems to be pretty helpful in general. The forum is the best advantage, because it's a pretty big community of coders share problem/solution there.

Selenium was in use before Ranorex. Ranorex have a great starter's guide for people that have never done automation. Selenium problems will lead to huge stack traces and unclear errors, while Ranorex stripped out a lot out of basic Visual Studio, so the majority of errors are pretty easy to describe and fix.

The initial set-up is easy for an experienced person, and for technical QA, without a lot of automation experience. Ranorex is a great tool to learn automation with pleasure.

In-house implementation. It's great to have Ranorex paired with Bamboo and AWS

Floating licensing are good for running the scripts on different machines (runtime). For developing, we are using node-locked ones, because Ranorex requires Windows, so we need to buy Windows laptops. It's the biggest drawback of Ranorex that it's limited to one operating system.

You need to have several windows environments for development. You can use Ubuntu or Mac for running tests inside AWS windows box, but development is better or native windows.

Features that I have been using actively and bring the most value to me are:

• Ranorex API – using different functions that the API provides to manipulate with the elements on the web page
• Ranorex Spy – identifying the different elements on the web page and generating the element repository to be used in different tests
• Ranorex Reporting – generating the report that shows the overall result of test execution, together with as much detailed as possible result of each step in a test case

Firstly, I can say that Ranorex offers easy-to-use test automation software for developing and managing projects which enables more efficiency with implementing new test cases.

Also, the results of test execution are represented with more details and in a very concise and effective manner. Log failures, successes, info, warnings, screen captures, etc. are possible to use to make the reporting more representable.

I would definitely say that the existing documentation of their API has a lot of room for improvement. Sometimes, it is hard to decide which of the existing functions to use since the explanation of the existing functions is extremely short. So it is left for the user of the solution to try out different possibilities to make sure that the chosen function will fulfill the needs.

I have been using the product actively in my work about a year and a half.

No issues encountered.

No issues encountered.

No issues with scalability because the tool itself gives enough flexibility to work with. For example, if some new features are added to the existing system being tested, it is feasible and easy to add new elements to the already existing repository without any complexities. We can then use existing functions of the Ranorex API to manipulate the elements.

I would rate it positively since their feedback comes a very short time after the requested help, support, or answer via email or their forum.

I would rate it positively since their feedback comes in a very short time after the requested help, support, or answer via email or their forum.

From the beginning of the project, Ranorex was used as solution for test automation.

I wasn't involved in the beginning of the project.

The solution was implemented as an in-house one. There wasn't need to hire the vendor team since the project by itself is not that big or complex.

Since it is possible to reference the API from some other tools and solutions, instead of being forced to use Ranorex studio, we gained a lot on flexibility and re-using our existing tools and technologies in combination with Ranorex features which are relevant for our test automation process.

Compared to the benefits that the product brings, I would say that the prices are reasonable and justified. I think the great advantage this tool offers is that it supports multi-technologies so that it is possible to cover the test automation of variety of different applications and systems.

My rating is based on the features I use. There are some other features of the product that I haven't touched yet because of the way the test automation is organized on the project I have been working on.

I would suggest using this product because even though it is not an open source solution, the benefits of using it are achieved based on the products price. I was a beginner when I started using this tool and got used to the tool in a very short amount of time so I started working actively very quickly.

It depends on the way the tool is used on the project, but either way, I personally think that the period the user needs to get used to the tool is very low because of the support that is offered through user guides and Ranorex forum or customer service.

• Easy to use - without any dev skills you can automate some nice things
• C# or VB.NET is used for development, and you can find a lot of information online
• Fast email support and a forum with several experienced users and Ranorex employees on it
• Online webinars to help you get started
• We can combine Ranorex with Jenkins and JIRA. We can store our test results in a database, configure our email templates, and create libraries so we can easily reuse code.

• Automatic testing of a web solution every night and after every deployment
• Every morning we get a test status of our different brands. We've created status pages that read the test status from a database, so we get a clear overview of all the tests that have been running at night or after each deployment
• Everybody have access to our status pages and can have a look of the status of a specific test

More possibilities on mobile devices, as we have already encountered some problems with iFrames integrated in a web page.

We bought this solution more than a year ago, in March 2014.

It's at a high level, as we always get a clear and fast answer. There’s also a lot of activity on the Ranorex forum.

Setup and installation was straightforward. If you watch the online webinars, you can easily start with recording test steps. If you have previous experience with C# or VB.NET in visual studios, you won’t have any problems developing in Ranorex. Otherwise, you can find a lot of information online how to expand your recorded modules with additional code.

We did the implementation by ourselves, it was not that difficult to install and add the license key.

Previously, we had to check and test every night the same test sets, and after every deployment a basic check of several test cases was needed. To do that, we needed a full time person to do that. Now, we can focus on new functionalities after each deployment.

We did some tests with Selenium, but you still need a lot of dev skills to setup and write an automated test.

Try the free trial and have a look at the several demo videos.

Test Suite layout and the logs. It is easy to navigate through logs and find the bugs. Ranorex improved our ui automation by providing handy features such as WaitForExists, Exists, Enabled, Visible

We have a flex application and it is difficult to use Java/Selenium, Ranorex helped to automate these flex application and improved our test coverage to deliver a bug free application.

Their logs are not compatible with the continuous integration we use internally. We have to parse the log file to extract the details. And we can view those logs/test results only in the Ranorex add on enabled browser which is IE, we tried in Firefox we keep getting this version of Firefox version is not supported. Ranorex should at-least say which version of Firefox it will support.

I've used it for one year.

It's good - 8/10.

It's straightforward.

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.

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.