What is our primary use case?
Our usage was at least seven to eight months ago. We have web-based and desktop Windows applications, and automating the desktop applications was challenging. Ranorex provided the necessary keywords, especially for our shallow testing needs.
We did a couple of POCs using this solution. But at the end of the day, we went on with creating our own framework. So, we used it for a POC to check its working and feasibility analysis within our organization.
Ranorex is what we found more secure. They allowed installation on your machine, and the reports don't go to the internet. Being in a financial organization, we want our reports to remain confidential, not part of the public domain or public cloud. So that was one thing.
Besides the flexibility that Ranorex offers, I'm an automation developer, and I appreciate the flexibility in terms of customization and other features. On the other hand, Katalon, or Test Project, uploads results to the public cloud and has a dependency on adding your own keywords and functions.
What is most valuable?
Data security was prime for us. Being able to download and run tests on our local machines was a big plus. The flexibility Ranorex offers in terms of customization is outstanding. My team provides solutions to different teams, including those with limited technical expertise.
Ranorex's user-friendly interface allows even non-technical users to automate with a minimal learning curve. So, the learning curve is less. The solution is accessible even to non-technical users with a shorter learning curve.
What needs improvement?
There were a lot of issues we faced. One notable improvement would be better API integration within the tool itself, as we still rely on external tools like Postman.
Additionally, expanding language support beyond C#, Java, and JavaScript to include Python would be beneficial. An AI feature that automatically detects automation object properties and suggests actions would be a great addition.
So, in future releases, AI solutions for automated property identification would be helpful.
For how long have I used the solution?
We used it for about three to four months. We used the version 10.6. We used this solution for a short period, but we liked its security features and flexibility. It provides excellent support for desktop automation in Windows-based applications, which is a plus compared to Katalon. Katalon does not offer desktop-based automation.
What do I think about the stability of the solution?
The stability is quite good. So, initially, when we started, we were quite skeptical about the stability because we didn't know much about the features. But then it was quite stable. So we ran it one to five times, and it worked the same.
I would rate the stability a seven out of ten. It is a stable solution. We faced some minor issues, but in general, it was okay.
How are customer service and support?
The customer service and support are quite well. They're reachable, and they provide proper guidance.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used Test Project. There were several reasons for switching to Ranorex.
Firstly, we were concerned about data security as our previous solution sent data to the internet.
Secondly, it lacked support for Windows-based application automation.
Thirdly, making changes was complex, especially creating custom keywords. For example, if as a developer, I might want to create a keyword. If they had different formats, it would be quite a cumbersome process to add a custom keyword.
Lastly, the tool was discontinued, and the paid version wasn't appealing.
How was the initial setup?
I would rate my experience with the initial setup around eight out of ten, with one being difficult and ten being easy. It wasn't overly difficult; it's mainly an installation process with a learning curve on how to use the tool effectively.
It was deployed on-premises. We installed it on local machines. They have runners. So you can buy a license to run and trigger the execution from your own machine to different servers.
What about the implementation team?
From installation to having everything set up for automation, the deployment takes around one day at most.
You have to request Ranorex, the license key, and tell them why they need the solution. What are you gonna do with it? Then they'll provide you a license key, and then you'll be able to install it. So that's just one of the hurdles.
Then, you will get set up files. You can download the storage. You can easily set up by downloading or just visiting their site. With Ranorex, the main thing is that you have to request the setup, which is followed by a couple of details.
We managed the deployment in-house. We have experience with installing automation tools, so no external assistance was needed. Just one person from my team worked on it.
But we didn't reach the maintenance stage. We conducted a POC, but we haven't started full-scale automation, so there hasn't been a need for ongoing maintenance.
However, we did reach out to Ranorex's support for help with specific issues, and they were reachable and provided guidance.
What's my experience with pricing, setup cost, and licensing?
I'd rate it around five out of ten, where one is cheap and ten is expensive, not too cheap but not overly pricey.
Which other solutions did I evaluate?
We tried Catalog Studio, but desktop automation didn't work well, so we abandoned it.
What other advice do I have?
The advice would be that you should have automation testers or allow experts to start with an idea of the tool. After that initial learning curve, it would become much easier, like a piece of cake. Proper training is essential for success.
Overall, I would rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises