We primarily use this as client solutions for test automation and administration.
We using XPath standard out of the box with success finding the containers and its elements.
We primarily use this as client solutions for test automation and administration.
We using XPath standard out of the box with success finding the containers and its elements.
It gives us various options to work as a consultancy with our different size clients.
The application test automation is the most valuable feature as well as being the one feature we use the most.
While the product does well with its primary job of testing, when we are using Ranorex it would be nice if it would report directly in HTML. We have to use another tool for that and that means that the distribution becomes a little bit more complicated than should be necessary. It is a bigger factor especially when testing is more complicated.
So having either better integration with a secondary tool or having those functionalities added to the platform would be a nice addition and simplify our process. There is a basic reporting module and we are using JIRA in addition in order to change the report formatting. So we need to have an interface from Ranorex and JIRA. It is there, but limited. If Ranorex did the reporting directly, we could easily make the result more compliant with what our management team would expect with no additional steps.
We have been using this product for about six months on a daily basis.
It is a very stable solution and that is a reason why we are using it. While we normally use it for enterprise businesses, we might choose it as a solution for businesses with a range of 50 to 1,000 employees.
The product will scale very easily. We have some questions about the license type because we need two types of license to keep it going. I get a lot of tests from our management group and we find if you can skip purchasing some licenses, you can save some money. It seems to be that we need both licenses for one tester.
Working with customer support is very easy. They have a chat channel which you can talk to. They also have FQA so when you have some easier questions you can use that channel. When you have some specific testing that becomes a little bit more difficult. We are working with this and we are using it together with Siemens sometimes. To get to the right answers, that answer may come off of Siemens or off of Ranorex. It's not always really clear. Everyone will not have that same situation.
Katalon studio, we changed on support issues, when it became free
For me the initial setup is straightforward. There is more than just the testing administration to sets up, but also you configure the tech management and reporting management. It is a few things to do, but I am familiar with them so it is not hard.
We are doing all the installations and developing ourselves. So everything is in house.
for clients we integrate Ranorex together with Polarion ( a Siemens supported test studio) to automate tests in a HMI/PLC domain, using WinCC-OA -> HMI functional tests to automate, this also includes receipts (for BIO clients & test automation)
Vesrsion control between Ranorex / Polarion is an important issue.
There are standard and premium licensing plans on a fixed price. I am not sure of the cost at this time. However, in our case, we find we need two different types of licensing to meet our requirements for clients and management. It depends on the client because we are a consultancy and serve small, medium and enterprise businesses.
As a consultant, we may choose to work other products in addition to or instead of Ranorex. It will depend on client needs. So yes, we do evaluate other tools but Ranorex fits many situations.
On a scale of one to ten, I would rate the product as an eight for what it does for us.
For those people in the market looking for an application testing solution, I would recommend evaluating the product and the type of projects you will need it for. I would recommend making an evaluation and comparison with other products to be sure that the needs for testing can be covered in the functionality of the Ranorex. The Ranorex is a studio, of course, so you will have lots of options to apply in ongoing test management and test automation. In my experience, those issues are all covered in Ranorex.
We use this solution internally for our testing. We produce software.
The most valuable features of this solution are object recognition and the fact that you can memorize the objects. This is something that I have always had a problem with before.
It is user-friendly and the speed is pretty quick compared to other tools that I have been using.
One of the areas the service could be improved would be to have the training in Italian.
While this is not a problem for me, it is a problem for my team. There is no documentation in Italian. As we are based in Italy, it would be helpful to have training in Italian in some form.
The stability is in the range of eighty-five percent of what I was expecting. We still have some issues.
There will be two people executing the tests in another month or two.
Having Italian language support would make the solution a bit more stable.
The scalability is very good. It's probably one of the better tools I've seen on the market. Some are very, very expensive, and we could not afford it, because this was in the mid-range, it was a probable solution for us.
I didn't have very many issues. The two or three that we did have, we received a reply within twenty-four hours. That was perfect for us.
Previously, we used a different solution called iMacros. It's very basic compared to what I'm doing right now with Ranorex Studio.
It was half the price, but harder to use.
Overall, it wasn't the best solution for us.
The initial setup was complex, but not because of Ranorex Studio.
This was an internal problem for us because the installation required an administrator and I am not an administrator.
We had to repeat the process a couple of times as a result. For the Ranorex Studio side, it was fairly straightforward.
The deployment method was on-premises.
We implemented on our own, without the help of any consultants or partners.
We paid €3,000 (approximately $3,300 USD) for this solution. When you add the runtime licenses it will be €3,500 (approximately $3,900 USD).
At this time I am developing. We only have one license, but there will be two runtime licenses.
Having a local reseller who already knows the product and can provide in-house training would be a fantastic solution and would make the learning curve a quicker process.
The transfer of knowledge from one person to another.
I would rate this solution an eight out of ten.
Support is very quick. You can write to them and on the same day, they will respond. This is one of the best features.
The forum is very good as well.
Regarding other features, the solution identifies the elements very well. Creating and editing elements is very good. They offer automation solutions, and it's all in one tool.
The element library is quite nice.
They have some problems with some pages rendering the angular solutions. If there are many queries on the web page, Ranorex will not render the page correctly. I had about 1,000 queries on the page, and the solution was not able to handle it.
It has a lot of features that are enabled by default, which can help you identify the elements, but if the page has too many queries, it will crash. It might be better if these features were not enabled by default. You should be able to choose the ones you need. It seems the solution was not optimized by the developer.
The solution is very stable. The only issue is rendering pages if there are too many queries.
The solution is very easy to scale.
Technical support is very good, I would give them ten out of ten.
The initial setup was easy.
I had a problem almost one week after implementing. From the beginning, you must look at the webinar. If you don't watch the webinar, it will be hard to work with the solution at the beginning.
The solution offers a free 30-day trial.
We are using the on-premises deployment model.
I would recommend people try the solution. They have a 30-day free trial that an organization could use to test them out.
Make sure to watch the webinar before implementing the solution, even if they are experimenting with automating. It will make everything easy to understand. Ranorex has a lot of options which you need to understand and to optimize. You can't automate the optimization, which is why the webinar is so important.
I would rate the solution eight out of ten.
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.
Strong Element capturing feature of Ranorex Spy, Coding in C#/ VB .net, Easy integration with CI Tools like Jenkins, TFS, TeamCity, Supports cross browsers, Tool Stability, Powerful record and playback, Ranorex IDE, Visual Studio IDE Integration.
We have used Ranorex for one of our biggest client to automate Web (Asp .net, Sharepoint and Silverlight applications) & Desktop (Windows and WPF) applications. We had smoke and regression test were running on daily basis on Production environment. Now doing some migration on the existing scripts for CRM support.
Other OS Support, Ranorex Spy performance improvement (Especially for Silverlight controls)
Tests will fail if browser minimised, Parallel Execution Not possible (We could do are some extend if we use DOM method), From my experience, Ranorex Spy is slow when spying on Silverlight controls (ex:- Consider if 500 UI Elements are in an hierarchy & you are trying to spy 470th element)
for more than 5 years
not issues, but difficulties when I try to integrate with tfs
Performance was slow for Silverlight applications
not specific
7 out of 10
Technical Support:8 out of 10
yes, previously I was using an automation tool (build on VB .NET) which did not have capability for automating flash/ Silverlight/ windows applications.
Very simple
in-House
We have automated 15+ internal applications for our client, which reduced much manual effort on regression testing.
no comments
When I try Silverlight automation (5-6 years back) no tools were promising, (Including popular tools in the market), So chosen Ranorex. But now many tools supporting Silver light applications, So better if we do re-evaluation against latest tools in the market
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.
Need few upgrades to automate desktop applications
I've used it for three years.
A few times with Android and iOS devices, but Ranorex support resolved quickly.
A few times without proper scripting skills the build will be always unstable.
A few times with Android and iOS devices, but Ranorex support resolved quickly.
Ranorex support team is really supportive and resolve issues as soon as possible.
Easy installations no hiccoughs.
The ROI is being able to automate the web, mobile, and desktop applications.
We're really satisfied with the pricing as well and buying licenses is easy. If you have a large automation team try floating license and runtime license which is cheaper than premium license.
We tried using HP QTP and Selenium, but opted for Ranorex because of its reasonable price and the ease of use of the automation tool.
Go through the user guide and update your library files for your mobile automation process.
Element Identification, I really liked the way Ranorex created a way (XPath) to identify their solution for maintaining stored elements in the repository.
The product supports multiple repositories and the ability to sort and maintain the repository in a positive way. I used the repository in combination with shared functions to pretty easily create reusable functions, that only needed repository maintenance with code changes.
I would like it to be more intuitive to use, especially in test management. I'd also like the ability to maintain and access tests in a more intuitive/structured way .
We've been using it for two months.
It was unstable at times, locking out – especially on any virtual or remote desktop machines. The lockout required resetting Ranorex.
High – it was pretty easy to get help on things we were stuck on, especially in the early stages of product discovery.
High – it was pretty easy to get help on things we were stuck on, especially in the early stages of product discovery.
Straightforward, easy to setup, great support from Ranorex team for initial setup and initial training.
Implemented this one through an in-house team.
We evaluated many different products for the engagement. We went with Ranorex due to its relative ease of use, and its support for automating desktop/WPF applications out of the box.
My advice for implementation is to do a proof of concept first to ensure this product works for you.
Do your research, all products have their positives and negatives. Assemble a list of requirements, interview vendors and other users of the product, go through strenuous Proof of concept phase – evaluating and analyzing how well the product fits your current and future needs.
A non-technical person can record a test and execute the same. But, a technical person is required to write code module and test data.
As per my knowledge, we don't have a (Free) robust tool for functional and GUI testing in desktop application testing field. This is way better than QTP and Silktest when compared to in following aspects:
User friendly UI
Cost of Tool
Continuous Integration
Instant release of updated add-on as per latest technologies and browsers.
Full fledged trial product for exact 30 days.
Need support for other operating systems like Mac and Linux, and not just Windows.
I implemented this tool for several of my customers and I can see the ROI rightaway. The tool is very easy to use and test automation can be started rightaway and improvements can be done later on. Perhaps this is the only tool where I would reply on Record and Playback because it just does excellent job same as manually adding automated test steps.
We automated hundreds of regression tests using this tool and they run every weekend and every time the test fails, an email is sent out. Earlier we used to run one big round of regression test every quarter but now we do it every week. Huge savings!!
We had no issues with deployment.
I personally think that, perhaps, it is one of the most stable automated tools available in the market. You can rely on your tests and it won’t let you down.
We've had no issues scaling it.
I would recommend reading through the user guide, the guide is very comprehensive and provides a lot of examples of best practises Buy Runtime Engine licenses for execution rather than full Ranorex Studio license. Make use of Cross Browser Testing as far as possible (Automate once and run on multiple browsers). Use variables and data fields that have consistent names (like $UserName and $Password).
Use data-driven testing, which allows to run the same test over and over with different data while getting consistent and verifiable results. Use the data to feed and to validate the system. Create small and distinct tests and you can always combine them in the test case. By keeping the tests small and simple you decrease the overhead of maintenance. Don’t automate tests which are run only once, try to automated repetitive tests.

This review was helpful. We recently went with Ranorex for our testing needs. Any issues with object recognition have been resolved with assistance from their support team.