Katalon Studio Reviews

Katalon Studio's pricing is expensive. 

.I have been using the product for three to four years. 

I rate the product's stability a nine out of ten. 

I rate Katalon Studio's scalability a four out of five. 

The tool's deployment is easy but difficult for iOS devices. Deployment speed is pretty quick.

The tool's licensing costs are yearly. 

I rate Katalon Studio an eight out of ten. 

We use the solution for application code testing. Using it, we can test around 70 modules for our clients in the insurance business.

The solution has the best reporting features. With the help of recorded reports, we can analyze the insights.

They should include standard methods in AJAX controls for the solution.

I have been using the solution for two years.

The solution's stability in terms of UI changes needs improvement.

It is a scalable solution.

In comparison to other vendors, the solution's price is less. It supports multiple easy-to-learn languages. Also, it has the best API integration and UI features. Although, the debugging process is time-consuming for larger test cases. It takes a long time to begin the test from the start and navigate it.

The solution's initial setup has medium complexity. It takes work to identify AJAX controls and then implement them. There should be an inbuilt method or features designed to handle these controls providing us with a straightforward deployment process.

The overall time taken to complete it is ten minutes. Although, for multiple integrations, it might take 20-30 minutes. Also, its maintenance takes time in case of UI changes.

The solution is more affordable than other vendors.

The solution has the best web UI. I rate it an eight.

We use Katalon Studio mainly for functional testing.

For tasks, our manual testers cannot cover Katalon Studio helps us. It speeds up our testing. If we are testing a large application, it benefits if we automate it using Katalon Studio

The most valuable feature of Katalon Studio is visual testing. It compares the look and feel of an application which is useful.

We have been seeing some error pop-ups that are difficult to understand why they were triggered.

In one of our applications, the solution is not able to recognize some of the elements making it unable to use with it.

I have been using Katalon Studio for approximately eight months.

We have had some errors on occasion. There was a learning curve when using the solution that could have contributed to the stability issues. We had to learn to use the solution from scratch.

Katalon Studio is scalable.

We have seven people using this solution in my department.

Katalon Studio could improve its support. Their response time is slow when we have premium support which includes direct connection with the agents.

New Relic had better support.

We previously used other solutions before switching to Katalon Studio.

The initial setup of Katalon Studio is easy. There was some confusion when we were upgrading the versions. The implementation can be done in a few hours.

The price of Katalon Studio is reasonable. They recently had a price increase that might impact new subscribers. We are using a business license.

We evaluated other options before selecting Katalon Studio.

We have not had any issues with maintaining the solution.

My advice to others is to test the solution well before purchase and confirm all the elements needed from the sales team. We had some issues at the start.

I rate Katalon Studio a seven out of ten.

We use the Community Edition and use it for UI and API testing. 

The ability to build all libraries with codes and use them in many situations has been most valuable. It has a very good recorder and the ability even to connect with databases to test data and use it in your scripts.

It gives you full access to all the properties of the browser or the network so you can customize the API scripts or UI scripts.

What it lacks is the Selenium Grid capabilities. 

I have been using this solution for six months. 

This is a stable solution. I would rate it an eight out of ten for stability. 

This is a scalable solution. 

We have only used the documentation and community support for this solution and both are good. 

We have moved away from using this solution. The solution we are using now is super fast.

The initial setup is straightforward. Without using the manual, it took me approximately 50 to 60 hours to start being very productive. 

We chose this solution because of cost. It is an affordable solution. It was less than a thousand euros for a server which supports three live servers for a CI/CD pipeline. They do not charge for a license per developer. 

I would advise others take advantage of the ability to use modern software engineering practices with Katalon Studio.

I would rate this solution an eight out of ten. It has features that I haven't found in many other products. It's very advanced in my opinion.

I am the manager of a team that provides testing services to clients and we use Kalaton Studio for test automation (mainly for web applications) as well as Jira which we use for test management.

Most of our Katalon Studio deployments are based on a private cloud because we work with companies that have particular concerns about security and they prefer to use either private cloud or on-premises infrastructure with machines internal to the company.

Being based in Portugal, our team size isn't that big compared with other countries like Germany, UK, or the United States. Thus, we are not officially partners with Katalon, but sometimes our clients ask us to facilitate the reselling of Katalon Studio.

Katalon Studio's biggest advantage is its price. It's a good tool for the price, albeit with some limitations when you compare it with tools like Tricentis Tosca. However, these tools are in completely differently leagues, just like in football where you have the National league and the Championship league. For specific needs, given its price, Katalon Studio is a good solution.

One aspect that can be improved is testing for desktop applications. I would like to see them support more technologies in this area. For example, Tosca, in contrast to Katalon Studio, has support for more than 150 different technologies.

I have been working with Katalon Studio for about 18 months. 

It is a stable product.

We have previously used Micro Focus UFT One and Tosca, and we also have experience using Selenium and Cypress in specific situations.

It's tricky to say whether the setup is easy or not in an absolute sense. In some cases, it's very straightforward, and in general it is easy to set up. We usually take a few days for the installation of Katalon Studio.

We implement Katalon Studio as part of a comprehensive solution that we provide as a service for clients, and it is just one piece of the whole solution. The number of people involved in the initial deployment is completely dependent on the size of the project and the stringency of the security required, but it usually only takes one or two people.

We have seen return on investment, but it depends on the application that you need to test. It's like a car; if you buy an expensive car that supports hundreds of thousands of kilometers without expensive repairs in the garage, you get the payback on that investment. And if you buy an expensive car and you only want to use the car on weekends, e.g. 100 kilometers per weekend, you might die before you get return on that investment. So it all depends.

In terms of pricing, Katalon, Selenium, and Cypress all represent a similar level of investment. The software for these tools are either true open source or almost open source (because they charge a small fee), so pricing is a neutral point for me. The price isn't a problem. It's all about compatibility with the application undergoing testing.

If you took twice as many hours to finish something that in another tool you could finish in half the time, then it represents an unnecessary cost. What you don't spend in license fees, you may be spending in the service itself, or in people to support it. These are costs that may become evident later.

Other test automation tools that we evaluated are products that we have used previously such as Micro Focus UFT One and open source tools like Selenium and Cypress.

When it comes to Selenium, it is more of a scripting language, while Katalon is a keyword-driven solution in which you can use visual programming.

The biggest piece of advice I can give to others is to first analyze whether the tool is compatible with the application to undergo testing.

I would rate Katalon Studio a seven out of ten. 

I use it for automated testing. I am not using the latest version because their patches come out rather quickly. I can't patch as quickly.

I like the feature where you can define a model that represents your website and then reuse the components from the model. It makes creating more test cases easy.

One improvement would be if it could support more programming languages such as JavaScript or Python. Right now, it is only on Groovy, which I think is not a too popular language. 

Other than that, we would want to see new features in every update. We would welcome any kind of improvement in terms of performance, etc.

I have been using this solution for a year.

Its stability and performance are okay and acceptable.

I am not in a good position to comment on this because I didn't try that out. Currently, we have less than 50 users. 

They are pretty good. They did address my problem. I am satisfied with their support.

It is actually a complex setup. If you want to do it in a good and sustainable way, it is complex to create a model, but if you want to just test things out and very quickly try out this product, then it is easy to get started. So, it is complex to create something that is sustainable. 

Overall, it took about one and a half to two months, which included many test cases implementations. The setup was done within a week.

It does require maintenance, but the maintenance of the server is up to your company policy. It depends on how often you patch your server, and how often you upgrade Java. The maintenance of the test scripts depends on how quickly the product changes. So, it varies.

I was using help from the proprietary vendor.

Its pricing is quite reasonable. If you require their help in getting started, then there is a professional services fee on top of the product license cost.

I would recommend engaging Katalon's services to get started. They do render pretty good help on it.

I would rate Katalon Studio an eight out of 10.

We are using it for API testing. I am just running it from my local machine. I am using it just locally.

It has been good so far for API testing on Mac. It is not that hard to learn and use. There is so much support out there, so if anyone wants to start using it, there is enough help.

Currently, I'm the only one who can use it because I have a Mac. It is giving a hard time to my team members who are on Linux. My team members are using Linux, and Katalon doesn't support Linux very well. It keeps on crashing. It crashes and shuts down almost every time they save their work, so they are not able to use it. It should have good support for Linux. We don't know what the problem is. If the Katalon team can pick up this issue, it will be very helpful.

It is a bit slow. The other tools on my Mac are not slow, but Katalon is slow. 

It has been more than six months.

I worked on Postman, but for RPA automation, I just started working with Katalon.

It was easy. I just had to double-click on Mac.

I am using the free version.

It should support all operating systems. Most of the developers use a Linux machine, but it doesn't support Linux. I would like an update from the Katalon team about why it is not working properly on a Linux machine.

I would rate it a six out of 10. It is a good product, but it needs some improvements.

For Katalon Studio we tried using it for record and play tasks. We could test it on Windows and different operating systems, such as macOS.

I did a small POC and during that time I found the product to be very easy to use. I'd describe it as extremely user-friendly.

There's a lot of information that is readily available on the internet, and therefore it's easy to learn about the product itself.

The scalability of the product is good.

The solution was quite stable throughout the time I used it.

We found the installation process to be quite simple. There is also very helpful online documentation that can help you if you ever get stuck during the implementation process itself.

As of now, the product has a complete packet and they could develop more on it. It definitely could improve the interface as well for mobile. While I didn't use it too much while I was working with the solution at the time, I am using mobile a lot now, and I see how helpful it is to have a good interface in place. 

The price of the solution is a bit high. It's one of the reasons we decided not to continue using the product.

I didn't use the solution for very long. I did a small POC for about one month or so.

The stability of the solution was quite good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable and the performance is great.

The solution is quite scalable. If you go ahead and use the paid version, you can expand it as you need to.

At the time, we had eight to ten people using the solution, however, we are no longer using it, and therefore do not have plans to scale or increase usage.

I personally never dealt with technical support. We had a team member in DevOps that would sometimes touch base with them. I can't speak to any personal experience, however.

We have used, and continue to use, an in-house automation tool. When that company developed our SIEM work, we built custom SEIM for work in Java and Selenium.

We simply tried Katalon as we were using different operating systems and we wanted to try a solution that worked across them.

The initial setup was not complex at all. The installation was very easy. The configuration, as well, was very straightforward. There are videos online that really help in walking you through the process. If you get stuck at any point you can watch them and they really help navigate you through the process.  

I can't recall exactly how long the process took to complete. 

In terms of maintenance, basically, there was one DevOps employee who was doing everything related to the maintenance part. We also had a manager heading it up. We were basically in different scrum teams and we were working on the same product. We only needed one person to look after everything and manage it as necessary. 

Originally, we did pay a licensing fee, however, the company decided not to continue with the product in the end. For us, it was too expensive.

On Katalon I didn't work much. I did a small POC and it was just for one month. After that, I switched back to our native and our custom in-house automation tool.

We didn't deploy it on the cloud due to the fact that initially, it was freeware, and then it got paid. At that point, our company was not interested in investing that amount of money into a new product when they had their own custom-built solution. They were parallelly building the automation framework in Java and Selenium. They're using test engines for reporting. Going forward, we will be using this framework and not Katalon.

I would recommend the solution to others. I would rate it at an eight out of ten.