Ranorex Studio Review

All our automation teams' suites are now more robust and accurate, but they need to focus more on the coding modules.


Valuable Features:

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

Improvements to My Organization:

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.

Room for Improvement:

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.

Use of Solution:

I've used it for around two years.

Stability Issues:

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.

Customer Service:

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.

Previous Solutions:

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.

Initial Setup:

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.

Implementation Team:

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.

Cost and Licensing Advice:

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
1 visitor found this review helpful
Add a Comment
Guest

Sign Up with Email