Katalon Studio Reviews

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 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 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.

We use Katalon for automating our website. The environment that we use it in is an website build in Node.js.

Previously, we had no automation solution for the web. Therefore, this application has helped a lot in automating the web.

The best feature is the split up between test cases and the test object. This allows us to easily change an error.

Support options need improvement. It is sometimes hard to find a solution to any given problem, thus you are forced to use another solution.

None whatsoever.

None whatsoever.

I did not have a previous solution.

There is no cost for setup or licensing.

I did not evaluate other options.

My advice is when you need a solution for a web automation tool, then use this one.

I use it for website end-to-end automation and continuous testing via integration on the VSTS CI pipeline. The tool is fully integrated in our tool process.

It provides us daily feedback on the status (failing/working) of the core features of our websites. A great tool for a non-technical tester to learn automated testing. Also, it is great for a technical tester, because it allows great customization.

Video capture on failure is a must have. A picture is worth a thousand words. A video is worth a thousand pictures (literally).

Object Spy is brittle. When I try to capture objects, I have to proceed multiple times before it works.