Katalon Studio Reviews

We primarily use the solution according to customer requests. We don't use it for a specific feature; we tend to use it when and if we are requested to. The client dictates that on their end. It's largely used as an automation testing tool. That's how it is meant to be used.

The solution has very good integration capabilities overall. 

The client has an extremely stable testing framework, and therefore they rely on Katalon to get the results. The reporting is very good.

The initial setup is pretty straightforward and easy enough to complete.

The stability, overall, seems to be reliable.

We haven't found the scalability to be lacking.

The solution could always add more features. It seems to lack a few requirements that a typical customer would want. Compared to other solutions, this product is lacking.

I'd like the integration with Jira to be a bit better. 

The pricing could be slightly improved. 

I've been using the solution for about a year at this point. It hasn't been that long. We tend to switch back and forth, between solutions. We tend to switch month to month.

I haven't come across any stability issues. Our clients haven't complained. It's pretty much big and glitch-free. It does not crash or freeze. Our customers have found it to be reliable.

We haven't found any limitations with the scalability. Our clients haven't hit any barriers as of yet. It's my understanding that the solution can scale. 

I've never been in touch with technical support in the past. Therefore, I can't speak to how easy it is to get in touch with them, or how knowledgeable or responsive they are. Unfortunately, I have no insights to share. 

Our team often Googles questions and can find answers online if they need to.

We did not find the initial setup to be overly complex or difficult. it was very straightforward. It was simple.

We have a team that can Google questions and find information online pretty easily if there is any maintenance that needs to be handled. We tend to handle the maintenance aspect for our clients. 

It's my understanding that the pricing could be improved upon. I cannot recall the exact pricing. I cannot speak to the cost or licensing terms. We're just basically maintaining the solution for our clients. 

We are just end-users and use it according to our client's requirements. We don't have a specific business relationship with Katalon.

Some customers use ALM, and we use Jira, due to the lower price. These help us with project management aspects. This solution isn't well known, as it might be in other countries. 

This solution is very useful for companies, such as banks or insurance organizations, that need something that can be used for commercial purposes. It's a good solution for enterprise-level companies.

I'd rate the solution at a seven out of ten. It's okay, however, if it offered more features to its customer base, it would be much better.

We evaluated Katalon Studio along with Postman and SoapUI to be part of our testing framework. We used it mainly for microservices, API automation, and testing API endpoints. We click one button to have it run all of the tests and generate a report.

Katalon Studio is useful because it helped us to generate reports to see which test cases passed versus which ones failed. It gives a good graphical representation of the results.

The most important feature is the Jenkins integration; it is pretty straight forward and allows us to run nightly builds.

The integration with Slack is very helpful.

The Katalon Analytical Studio, which is directly integrated, offers better reporting capabilities, which is a good feature.

We found that Katalon Studio crashes a lot of the time and it would be very good if it were more stable. When it crashes, the tests are not always saved and this means that you have to start again from scratch. It would be helpful to have an automatic save feature.

We used Katalon Studio for about two months while we were evaluating different products.

This solution crashes often and stability is something that needs improvement.

I would rate the stability a six and a half out of ten.

Scalability depends on the scope of the project. It is not meant for load testing. However, if it can be integrated then you would see that it's more scalable in that aspect. Because it is just for API endpoint testing, it is not as scalable as one would assume. Again, it is for endpoint testing as opposed to load testing.

We had a team of four or five people who were using this product. They are test engineers with similar roles. 

It is a growing community. There are documents available but I would say that the community is pretty small as compared to what Postman has.

Prior to this solution, we were using TestNG. It is more about writing automation code as opposed to using an automation tool. Using it means that you have to write a lot of code. Code snippets will do for some testing but if you want to do regression testing then there is a lot more to do. One of the reasons that we implemented Postman, and evaluated Katalon Studio, was to get away from writing code and using something more stable.

The initial setup is quite straightforward.

We deploy per release, where every two weeks we deploy a new release.

Our implementation strategy is to create the test case first, then to create a test suite in the object repository. We can add all of the endpoints, and the calls for the endpoints. We run the tests through the suites, which will test all of the test cases. It is then run with the Jenkins integration and Slack integration to get the results, and what has passed or failed will be clear.

The implementation is straightforward if you are using it from the local machine. You can download it directly through the provider interface.

If you are running it through the Jenkins you will require a plugin to be downloaded. Jenkins supports plugins that include the Katalon plugin, and once downloaded, you enter your code into the repository and run it from there.

We were using the free version of this tool.

We evaluated Postman and SoapUI along with Katalon Studio. Ultimately, we chose Postman because it has been in the market for a while, it has good open-source documentation and has a more active community. In general, people trust it.

Products such as this one are a byproduct of artificial intelligence. It comes up with very nice code snippets that we can use, and it is good to see the industry moving forward in this aspect. The future is AI and Katalon is a part of that.

When it comes to testing RESTful APIs, this is a good solution but in the alternative, Postman is out there. That is the one that we ultimately chose to implement.

I would rate this solution a seven out of ten.

We primarily use this solution for user acceptance testing, web testing, regression testing, and mobile app testing.

The most valuable feature is the capability of doing end-to-end testing for both web and mobile apps.

The basic framework and project organization is very good.

Data design testing capabilities are useful.

The maintenance of the tools can be improved.

We have had some issues when it comes to stability i.e when project has lot of items in workspace, which is something that needs to be improved.

I have been using Katalon Studio for just under two years.

At times, Katalon is a little bit non-stable i.e When a project has lot of items in workspace, it takes a while to save . We have had a couple of issues related to instability for more complex models, but we are hoping that it will get better. Because of these issues, we are not able to integrate this solution into our platform.

The scalability is okay for our immediate purposes. We have a maximum of ten users who are all test engineers.

We did have a couple of questions for technical support but we did not have direct interaction with them. Instead, we asked them through the web community forums, and some of them were answered.

It was a difficult problem so that may be why not all of our questions were answered. Also, you don't always get reliable answers from the community. For example, we followed some free advice to help with the implementation and it was not good for that purpose.

Prior to Katalon Studio, we were using UFT for our testing. We switched because Katalon is free and doesn't cost any money. It works in the meantime, and they have the capabilities that we need. The cost was definitely a factor.

The initial setup is really simple, which is one of the good things about this product.

It was really easy to implement and use. I look for information online from Katalon before we started our testing.

We completed the implementation using our in-house team.

It takes two or three people to deploy and maintain this solution.

There is a free version of the tool to use and support is available through the community forums, but there is a licensed version as well.

We did not evaluate other options. We needed certain capabilities and we found Katalon to be acceptable.

It is a good product. I would recommend it because they are promoting that they will update it for free, for life. We have had issues with stability but it might be better with the licensed version.

I would rate this solution a seven out of ten.

1. Katalon Studio provides the team much flexibility to adapt to various situations to address a problem appropriately. There are certain test cases that can only be tested manually, but Katalon allows the team to automate as many test cases as possible.
2. The “Debug from here” feature reduces the debugging time considerably.
3. It produces detailed and useful logs, helping the team to detect a defect’s root causes easily.
4. It scales well, supporting the execution of large test suites.
5. It can be used to verify various issues, ranging from minor errors like typos to performance and stability problems of the system.

Before using Katalon Studio, we spent weeks to verify all test cases manually for every major build. Now, we need only several days to fully perform regression testing, reducing the time to market greatly.

While the web testing is great, we expect more from the API testing.

More than six months.

No. It's very easy to deploy.

Rarely.

Not yet.

They provide very good customer service.

Excellent, since they promptly respond to our requests.

Robot Framework. However, it required more technical involvement, so the dev team needed to join and spent time setting up before our QA could join.

In-house.

After several years using Katalon Studio, the team now already automates more than 20% of the test cases, saving much of the verification time as well as exceeding the target set when starting the test automation effort.

The tool has been completely free until now.

TestComplete and UFT. They're all costly.

We are currently trialing the solution's test automation functionality.

The recording feature of this product is very valuable for our testing purposes.

We would like to see improved integration with various reporting tools; this would make our testing data more complete.

We have been working with this solution for six months.

We have found the solution to be stable during our trials.

The solution is easily scalable in our experience.

We have found the technical support for this product to be very good, and knowledgeable.

Positive

The setup of this solution was very simple for a simple web application, and deployment only took 20 minutes.  However, for multiple applications, the lack of integration makes implementation a longer process.

We would recommend this product for a standalone web application use case, but we would suggest that any business using multiple web applications, should try the solution beforehand using the open-source version that is available.

I would rate this solution a seven out of ten.

We are using Katalon Studio for test automation. There are multiple use cases including creating Selenium scripts to help guarantee RPA frameworks.

The most valuable feature is the Element capture. It is capable of scanning the application, recording, and capturing the elements.

You can develop a Selenium script and execute it in Katalon Studio.

There are multiple ways that you can guarantee the functionality of RPA frameworks.

Katalon makes it easy for the automation engineer to create automation scripts.

There are lots of script creation options including for the desktop and the API.

It is easy for a non-technical person to use and adopt.

It is difficult to identify elements on websites that use Angular or ReactJS because they don't have an option to view source code.

There is no centralized repository for documentation, which is something that would assist users.

I have been using Katalon Studio for about a year and a half.

This is a stable solution.

Katalon Studio is scalable because of the cost, and that you can execute Selenium scripts.

We have three people in our team who use it.

My opinion of the technical support is that it is average. I am satisfied with it.

Katalon Studio is a free tool.

Overall, it is a good tool in the market for test automation.

I would rate this solution an eight out of ten.

We have used this tool to automate the regression test suite for our testing environment. In the coming future, we are willing to do the same in staging and production environments.

It definitely improved the organization in terms of time. We are now performing automated testing in 15 minutes, which were previously taking a long time when doing it manually.

We liked the built-in framework. 

Also, I personally like the 'Object Spy' feature of this tool. It makes it easy to find an element on the web page.

Katalon Studio should improve on its supported platforms. It should start working on Silverlight automation as well.

Our primary use is for web automation.

We are an IT consulting services company. As part of our services, we provide testing services. That is why we are constantly looking for some tools and frameworks that might fit with our clients' needs.

We call ourselves agnostic, which means we are not going to be with only one provider. However, I've seen very powerful things behind the Katalon.

I find Katalon Studio to be a very complete product. Our clients have requested all types of testing, including mobile, desktop, and API testing and all of those are covered by Katalon. I find that very valuable, very complete.

I've seen that our clients are not truly aware of the power behind Katalon. Many of the clients are now ready for the traditional Selenium, perhaps a more friendly layer like Cucumber or SpecFlow. But I think they will understand if we start doing automation with Katalon and they would be much more interested. The automation developers are starting to have really high demand and the salaries have increased, so with Katalon they might be interested in two things - the velocity of testing plus bringing manual testing to the automation world.

I have been using Katalon Studio for about a half year, now. I use it for demo purposes with our clients.

We previously utilized Katalon for demo purposes. We also used Selenium, not Selenium HQ, but Selenium alone. And I think we are utilizing Cypress and Cucumber with Selenium, in different flavors of languages, et cetera.

I haven't precisely checked the business model behind Katalon, and I would like to understand that as well, because most of our clients ask for licenses and prices, and we don't know. From my understanding, the basic version is free, but it would be interesting to understand the full package.

On a scale of one to ten, I would give Katalon Studio an 8.