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 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 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 are using this product as a tool to teach students about testing. We are not teaching them how to use this specific tool. We are helping the students to understand how to find the right tools to do the testing on what they develop.  

fast learning curve tool (and profesional) for students new at the subject

The most valuable features for me are that Katalon Studio is powerful and yet easy-to-use. This solution — even in comparison to Selenium, which we were using previously — is a little bit more simple from a user's standpoint. It is interesting because it is not only focused on the end-user but interface testing — and that includes API testing. Even if we do not generally need to use it, it is interesting. We are a university and we have a very small department that is doing development testing of software. Most of the projects are not API-based. We still are employing some old client-server versions and software architecture. But the capability is still interesting looking forward.  

I have worked with the record and replay feature which helps to create test cases. It is quite useful for assisting in testing a user interface and a very good experience for students' understanding of procedures.  

I really do not know what every user who is using this product might need to make it better for them. I do not think this is an easy question to answer for users globally. I do not think there are any features that we need. We had a small problem with an update of the web browser, but we managed to figure it out. New features are not part of our usage for the product.  

I think the one thing that is more problematic for the product is the online documentation. It could be more centralized and better or just easier to find.  

We have been using Katalon Studio off and on as a teaching tool at our university for maybe two years.  

It is OK.
We had 3rd party problem (browser update) that broken the test case. But it was fixable.

We do not really have a reason to test the scalability, but it should be quite scalable. For the training project, it is only something students do for a few weeks. It depends on the team, but between two and six weeks, and no more. We get an average of about fifty students in their third year right now. They launch an initial development project including testing activity. The use of this kind of tools is optional and tool selection depends on the student group. The do not develop more than 2/3 sprints.

Within the department, we were previously using Selenium a few years back for teaching testing. We actually switched to Katalon from student suggestions. In the future, we may change again.  

The most important thing about the product is that we can use it to teach about testing. So it was not imperative to switch but it is also good for students to have varied product experiences.  

The initial setup takes a couple of weeks. That is not really too long for a product like this. It was relatively easy to do.  

One of my colleagues is in charge of teaching software engineering testing issues. When the students are tackling the testing project, they sometimes suggest using different tools. Some years ago it was Selenium, nowadays it is Katalon. Of course, there are other tools that perhaps in the future we will suggest to the students to use in their projects. We are not teaching them to be professional users of Katalon and we will continue to evaluate tools and take suggestions for future packages.  

In looking at Katalon Studio and comparing it with Selenium, I think Katalon is better. The capture and replay functionality for sure sets Katalon ahead. As far as the API testing, we have not tried to explore that part. I have only heard that Katalon is very powerful in that capacity. Katalon is easier to work with and to integrate. Those are the main strengths and the differences we have found between the products.  

I would rate Katalon Studio as an eight-of-ten overall on a scale from one to ten where one is the worst and ten is the best. It should be considered that we are not very demanding users. We have not put a lot of stress on the product in our testing.  

To get a nine or ten, if they could provide some capabilities with artificial intelligence to help to assist testing models that could help people to improve in finding the best-case scenarios. Version testing might be an option as well. But Katalon is much closer to getting ten points than Selenium.  

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.

I am automating my current project with web application manual testing.

It's a requirement gathering application and has lots of workflows for the user.

Manual testing requires a lot of manual processes and time to complete the test cycle. With the help of Katalon, the process is running more smoothly and is less time-consuming.

Regression test suit saves lots of time to complete the whole testing with inbuilt reports in PDF format.

The Keyword feature is very good to use in your test cases. 

There are lots of inbuilt Keyword features already there to use, and one can write their own for use in respective test cases.

Less Java knowledge is required to write a keyword.

This solution is very user-friendly to learn and implement, and less technical knowledge is required to handle automation.

My recently-updated Katalon studio version hangs a lot and is not a stable version.

The support system should be improved in many areas such as Katalon Studio forums and the Katalon community page, where developer responses take a lot of time to reply to user questions.

Actually support response time is more than expected.

The stability is great.

The scalability of this solution is good.

Technical support for this solution is ok, but it could be improve.

I used Selenium, but Katalon is much more user-friendly.

The initial setup of this solution is straightforward.

Dont know about that

NA

It is freeware software, so start using it.

I did not evaluate other options.

Great tool to start automation, easy to learn and doing.

The functionality of the data is very good. You can upload and disperse data using the solution. The reporting is excellent as well.

The browsing is messy. The solution tends to rush the tests on multiple processes. That doesn't work in most cases. They need to write a different script for the same test case on the cloud and another script to run the test on Firefox, for example.

Also, in terms of reporting, in the documentation, it's mentioned that Katalon takes screenshots if the test case fails. But not on all test cases. I need to take screenshots manually.

Often, running parallel test cases at the same time doesn't work. If it launches the first test case and it tries to launch the second test case at the same time, for example, the first test case will finish but the second will not stop. A lot of people are talking about this issue on the forums.

The application is prone to freezing when it loads.

Katalon doesn't support testing of hybrid applications. It's a limitation.

In general, the solution is stable.

For one machine it's good and easy to use. With this solution, you want to limit yourself to small tests.

Technical support isn't very good. I've had problems where I couldn't find answers within the community. I've never used the ticket support system, although they do have one. I've mostly relied on the community to source answers.

We previously used Selenium HQ.

The initial setup was a local setup; I simply downloaded it from the website.

I implemented the solution myself.

The tool is free to use.

We are using the cloud deployment model.

I would recommend the tool. For a free solution, it's very good.

I would rate the solution eight out of ten.

We use this solution for functional testing on some backends, APIs, the ServiceNow GUI, and other web GUIs. 

We have it running on a few machines, in-house. Each developer downloads it to their machine, and we also have it running on a test server. 

This solution is written in Groovy, which means that we can write Groovy scripts that work with it. We can write code in Java and it is easy to link to other JARs that we find on the internet, which is very handy.

From a user's perspective, this solution is better than Micro Focus UFT.

The documentation for this solution could be improved. However, it is a freeware, and the documentation is still better than that of UFT.

At the moment, this solution only works for web-based products. It's sort of like a Selenium wrapper, which is quite well done.

The Object Spy is rather frustrating to work with, so I tend not to use it. Instead, I just go and look at the objects in the HTML code, in Chrome for example. A more user-friendly Object Spy would be an improvement.

I would like to see the extension to other GUIs such as Windows and SAP.

The stability of this solution is good and improving.

This product is installed on your own client, and it runs fine there. Scalability is not really an issue. There are two of us using this solution at the moment, and we plan on maybe going up to three or four. There is only a certain amount of testing and automation required for our project.

Technical support for this solution is mainly through forums, and the forums are quite good. 

We are trying to get away from Micro Focus products because they're extremely expensive. For functional testing, we're migrating to Katalon Studio, for example. 

In the organization as a whole, people are using UFT from Micro Focus, and they are paying a lot of money for it. From the perspective of the user, I would say that this solution is better than UFT, and would encourage people to migrate from UFT to Katalon.

Personally, I have also used Rational Functional Tester, Tricentis Tosca, and Ranorex.

Tosca has a very good analysis, but if you're working with complex web GUIs, such as Angular for example, then Tosca is a pain in the neck. Tosca is more for test analysis.

Ranorex is a good product and it is more flexible. I believe that it can handle Windows GUIs, which Katalon cannot do at the moment. However, Katalon is free, and they are also implementing Winium if we should have the need for Windows GUIs.

The initial setup is straightforward. You just download a ZIP file, copy the contents of it into a directory, and you're ready to go. It is a bit like installing Eclipse. The deployment is quick.

This product is freeware, so there is no charge for using it.

There is a paid service available that offers a cloud database where you can store your test cases, pull your test executions, get reports, etc. We're not currently using this service so I cannot comment on it.

I was recently tasked with looking at different testing tools, and I evaluated several including Katalon. Once I tried it, I liked it, and so far we've been happy with it.

My advice for anybody who is considering this project to have some familiarity with Groovy and Java. If you don't like coding then it will not be the product for you. Otherwise, in our experience, it's a good product. It is well thought through and continues to improve.

This solution semi-automatically updates to the latest version, so it is always up to date.

I would rate this solution an eight out of ten.