Katalon Studio Review

Good reporting as well as integration with Jenkins and Slack, but it crashes often

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

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

What do I think about the scalability of the solution?

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. 

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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.

What's my experience with pricing, setup cost, and licensing?

We were using the free version of this tool.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Katalon Studio reviews from users
...who work at a Computer Software Company
...who compared it with SoapUI Pro
Learn what your peers think about Katalon Studio. Get advice and tips from experienced pros sharing their opinions. Updated: September 2021.
534,226 professionals have used our research since 2012.
Add a Comment
ITCS user