Ranorex Studio Reviews

Through Ranorex, we are automating our test cases done for our internal CRM solution. We are using the keyword-driven approach available in Ranorex, and we get benefits from the essential support for Dynamics CRM (all versions). We are using also the runtime feature that runs the test suite independently on the server.

With this product we are continuously getting rid of manual regression tests that had to happen each deployment manually by key users. It brings more accuracy in regression tests, more time for involved people for their daily tasks, and more confidence to the application. In the future we plan to incorporate automatic execution in the continuous integration process.

It needs a better connection to TFS.

We have been using it for six months in my department.

The application is more stable by comparison to other products on the market that we have considered for test automation.

Communication with the Ranorex support was very effective and straightforward in early phase of incorporating Ranorex into our internal infrastructure. Ranorex is providing us with best practice sessions and code reviews. We appreciate their very quick purchasing cycle.

In the beginning we had small problem with configuring Ranorex License manager in our infrastructure due to our firewall and proxy settings, but with the help of Ranorex support we quickly found the fix to solve the issue.

We implemented it with an in-house team with the help of a vendor team, but I expect that for companies with less strict network security policies, it would be less of a problem.

With the incorporation of Ranorex and automation testing in general we are saving a lot of time for our internal people. ROI is calculated at about one year approximately.

We have purchased the premium license with an enterprise package, which includes special care from Ranorex such as code review, high priority in issue solving etc.

We had an evaluation period to choose most suitable product from ones available on the market and during that we have tried many of them. We have discovered that Ranorex has native support for all technologies and products used within our company, such as SAP, all Microsoft Dynamics products, SharePoint, Kentico, web based portals and others including support for mobile testing. Also, it beats the others in stability, because other products crashed very often once using recording module.

If you are looking for an automation tool that is easy to implement, easy to understand, and works with most of technologies on the market, Ranorex is the appropriate solution for you. So far I can only recommend this product.

Live tracking along with capturing the RX path of objects, and cross browser testing is the most valuable feature of this product. Also, its seamless integration with any test management tool is the best feature.

In total, the test execution times of the test automation projects were significantly improved. In conjunction with a new test case design, ease of use, the functionality of the software and C# as the standard programming language, new test cases can be implemented more effectively than with the older software.

The results up to now indicate that much less time is needed for execution with Ranorex robust tests compared to the previously used automation tool

Object recognition of Outlook add-ins instead of raw text recognition could be better. Ranorex should also provide features for Windows Mobile automation.

I have been using this tool for the last two years, and I love the way that they have frequent updates that provide new features and support for the latest technology.

No issues encountered.

No issues encountered.

No issues encountered.

Customer Service:

8/10.

Technical Support:

Ranorex has provided on-line training for my company, particularly for test automation, so 8/10.

I've seen and used many different test automation solutions like HpP QTP. Not only is Ranorex's solution one of the most powerful and easy to use, it has one of the lowest cost entry points resulting in a quicker ROI.

Also, their end user support and communication has been second to none. C# language support is an added advantage of that.

It was very straightforward, just click on the EXE file and it will do the rest automatically.

The initial set-up was quiet simple, and there was no need for any external help.

We found that the tool could also be used in reproducing defects and automating user cases, which were very hard to do manually.

Ranorex doesn't provide automation for Windows Mobile, and lacks some of the basic functions like table comparison etc. Although one can achieve this through C# or VB.net, it would be better if it provides the UI comparison. However, Ranorex uses power of C# to built a highly competitive Automation tool.

You should go for it and it will not let you down.

It has a good UI recognition and it is easy to maintain the tests. The RanoreXPath is very powerful and makes it possible to set-up a strong UI recognition even when the design is slightly redesigned. Also reporting is very useful with good description of the executed steps and screenshots when tests fail.

It made it possible to automate a lot of processes in our Windows Forms applications, and we also plan on using it in a web application. Now, we’re able to execute tests overnight which would be forgotten if we only had manual tests.

It would be nice to have a way to indicate the coverage of the tests of the application. Currently there’s nothing available for this, and it’s difficult for Ranorex to have a good implementation of this feature. We need to say that Ranorex gives a lot of support and listens to their customers when there are requests for features.

We’ve been using this for about two years. We started by using the trial version, and making some test cases. and soon it was clear to us that this was the tool we needed. After two years we’re still expanding the use of the software. We're also constantly updating the software.

At first we needed to become familiar with the software and it took some time to set-up a stable test environment but we were able to become this in the last few months. We’re using Ranorex in combination with Jenkins to trigger the tests and we’re able to run the tests without a real screen.

Customer Service:

Ranorex are very polite to their customers.

Technical Support:

Their support is always there for you. Even when we were using the trial they gave support while creating some tests by remote sessions etc.

The set-up of Ranorex itself was very straightforward. but getting the tests stable on a remote server required a bit of practicing. Also, we had to find a way to run the tests without a real screen and use it with Jenkins but actually in the end it’s not hard to learn this at all.

We implemented it completely by ourselves. The implementation depends a bit on the requirements of the organization I think.

Thanks to Ranorex we were already able to find some bugs we wouldn’t find by our manual tests. It helps us to discover bugs in parts of the software we’re currently not focused on.

The pricing for this product is OK, it might not be cheap for a small company but extending the licenses is a lot cheaper than buying it the first time.

We compared some solutions like SOAP UI and Selenium but for our use it was clearly that Ranorex was the best option. As Ranorex is based upon C# and the .NET framework and our software is also developed in C#.NET it felt familiar and testers could also get help from developers if required.

Ranorex is a very good product, especially for testing Windows Forms applications but also companies with web applications and mobile applications will be very pleased by the product as it has also perfect UI recognition for these platforms. It’s also easy to learn for non-programming skilled people.

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.

Customer Service:

8/10

Technical Support:

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.

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.

• 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.

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

It forced many developers to stick with conventions and organizational coding practices.

Less changes to the code when modifying a repository. Any minor change to a repository can result in a version control system nightmare, making it more difficult when working in teams.

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.

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

Customer Service: It's above average.
Technical 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.

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.

Customer Service:

9/10.

Technical Support:

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.