My main use case for Katalon Studio is to automate desktop applications, which was a primary requirement for us, and subsequently, we utilized it for web, API, and eventually mobile application requirements that came up later.

For a specific example of how I used Katalon Studio to automate a desktop app and the web API side, I was working with a US-based manufacturing domain client who had many web and desktop applications, and I aimed to automate their test case functionalities. I discovered that Katalon Studio was the best compatible and suitable tool, so I adopted it after the purchase, primarily due to its modularized design compatibility which minimizes the need for extensive coding and allows for quick automation delivery across web, API, and desktop applications.

Katalon Studio has proven effective in our deliverables, particularly in designing the framework where other tools typically require coding in client libraries such as Python or Java. With Katalon Studio, there is no such complexity, allowing us to organize projects modularly based on folder structures without needing to write separate code. The self-healing feature for web application automation and its built-in CI/CD ecosystem integration eliminates the need for external tools for pipeline setup.

Katalon Studio excels in CI/CD integration, providing an inbuilt ecosystem without the need for external setup, and it features a postings structure along with keyword and library availability. Newcomers to the team can easily adapt to the setup or project structure, which contributes to its popularity, along with its low-code or no-code capability that allows for a comprehensive platform supporting web, mobile, API, and desktop automation. The self-healing mechanism for test cases autonomously identifies issues with locators and ensures they continue functioning, which is impressive, along with the robust object repository.

Katalon Studio has significantly aided our team, especially when clients expect deliveries for CI/CD integration that requires automation test scripts to run on a daily schedule. The self-healing feature automatically identifies available locators for elements in the DOM, ensuring that test cases remain functional.

Katalon Studio has positively impacted our organization by facilitating faster delivery when clients have urgent requirements. We can deliver quickly based on urgency due to the features Katalon Studio provides. This has led to significant reductions in time spent on framework configuration, designing, and training individuals who are unfamiliar with the tool, helping us save both time and costs.

Based on my experience with Katalon Studio, improvements are needed, particularly regarding desktop application recording and playback, which should be more flexible and not limited to relying solely on .exe files installed on the system. We've encountered issues when connecting to remote machines where applications are installed, making it necessary for the tool to accommodate testing in such cases. This flexibility is crucial for service providers who may not have the option to onboard clients directly at their locations. Additionally, there is a need for improvements in mobile application automation compared to other applications available in the market.

I have been using Katalon Studio for a couple of years.

For 100 test cases we were expected to deliver within a month, we initially needed to spend 20 to 25% of the time on automation before delivering test case scripts, and thanks to Katalon Studio, that much time and cost is saved.

Katalon Studio offers a dual scripting interface that allows for both manual record and playback as well as automation or scripting. Testers can switch to manual mode or record and playback if they prefer, and for those comfortable with scripting, Groovy script support is readily available, which is a valuable addition.

My advice for anyone looking to use Katalon Studio is that if you're eager to deliver quickly without getting bogged down in scripting or framework design, this is certainly the tool for you—it's easy to adopt and start delivering soon. It is particularly beneficial for small teams or individuals who might not want to undergo extensive training to begin delivering automation features.

I would recommend Katalon Studio, as I have been doing for months to those who reach out to me for tool validation or automation needs, and I will continue to encourage others to explore it.

I rate Katalon Studio 9 out of 10 because there is room for improvement and some requirements that still need to be fulfilled; addressing these areas would make it a perfect fit for every tester.

I've been using Katalon Studio for two years.

My main use case for Katalon Studio is working on automation. I created and executed test scripts, used data-driven testing, and integrated runs with Jenkins for continuous testing. I use Katalon Studio reports to track and fix the failures. For example, in one of my projects, we automated the user login and product purchase flow using Katalon Studio. The goal was to ensure that the login, product search, add to cart, and checkout functionalities worked correctly after every deployment. I created reusable test cases for login, navigation, and payment, used test data from Excel for multiple user credentials, and set up the suite to run automatically through Jenkins integration. The automation reduced the manual regression effort and helped identify the broken flows early in the QA cycle.

The reason I chose data-driven testing and Jenkins integration for my project is that Jenkins helps schedule and run automated test suites whenever a new build is deployed. This ensures early detection of issues and consistent quality without manual intervention. It provides reports and integrates easily with tools such as Katalon Studio, Git, and Jira. I focused on data-driven testing, which allows running the same test cases with multiple sets of input data, such as different usernames, passwords, and payment methods. This increases test coverage, reduces duplication, and ensures that the application handles various data conditions correctly.

I wanted to do something automated for the things we list for sanity testing. Whenever a new build is deployed, a sanity check should be done. If the automated tests are already written, it makes it easier. The login and checkout flow in Katalon Studio using data-driven testing and Jenkins helps reduce manual regression time, ensuring faster feedback after every build. If any issue arises, we can inform the developers at the earliest.

The best features Katalon Studio offers include its user-friendly nature. It is very much a user-friendly automation framework that supports both beginners and advanced users. It combines manual and script-based testing, allowing easy recording of steps and customization using Java or Groovy. Its built-in reporting, data-driven testing, and CI/CD integration are extremely useful for managing end-to-end automation efficiently. The best feature of Katalon Studio is its ease of setup with both manual and scripted automation, plus strong integration techniques, which help the tester find reports easily. It is more focused on debugging, reusability, and reporting.

The reporting and debugging features of Katalon Studio help me in my testing workflow by providing test execution reports with logs, screenshots, and videos for failed steps, which makes it easier to analyze results. The report can be in formats such as HTML, PDF, or integrated into Katalon TestOps for tracking trends over time. For debugging, I use the debug mode to run test cases step-by-step, check every value, and inspect the console and log viewer for error messages. Katalon Studio highlights the exact failed step, provides stack traces, and helps quickly identify issues in locator data or synchronization. For example, in one of my projects, I automated a video upload and a preview feature in a web application. During execution, the test failed at the preview validation step. The Katalon Studio report showed that the preview element was not visible within expected time. I switched to debug mode, added a wait condition, and re-ran the test step-by-step to verify that the video preview loaded correctly before validation. After updating the script with an explicit wait, the test passed consistently, confirming all steps were successful and improving the reliability of future regression runs. Katalon Studio's report and debug mode help identify whether it's a timing issue or if we need an explicit wait.

A key feature I notice in Katalon Studio is its cross-platform automation, supporting web, mobile, API, and desktop testing in one tool. The record and playback feature is my favorite because I'm not from a coding background. It allows for quick test creation without coding, making it accessible even for beginners. The repository and data-driven testing provide centralized storage for test elements, improving reusability. We can run the same test with multiple sets of data, which is also significant. The integration part is excellent, along with reusable test suites and keywords, which allow modular and maintainable test structures across projects.

Katalon Studio has positively impacted my organization by significantly speeding up the testing process. The repetitive regression tests that used to take hours or days are now completed in a day or just two to three hours. The built-in reports and debugging features improved communication with developers and made issue resolution faster. With Katalon Studio providing detailed reports, false arguments have gradually reduced. Overall, test coverage, accuracy, and team productivity have enhanced, allowing for a more confident delivery of builds and shorter turnaround times. I think the company has a positive impact overall.

One area for improvement in Katalon Studio is execution speed. Larger test suites can take more time to execute. Performance optimization could make automation runs faster. Better integration and lighter resource usage would also enhance overall usability. I haven't found anything particularly frustrating, but sometimes large test suites take more time for execution.

I've been using Katalon Studio for two years.

Katalon Studio is generally stable. I've experienced some minor issues, such as it occasionally losing data and not showing it. However, this is not critical; restarting the application usually resolves it. I have not encountered any major bugs or crashes.

As for scalability, I cannot comment much because I use it as a single user. Katalon Studio seems to handle increasing workloads well, but I cannot speak for multiple users.

I have not had direct contact with Katalon Studio's customer support because everything provided on their website is sufficient for learning. I haven't had the need for support, and I think they ensure users can easily start with Katalon Studio. My colleagues also find it easy to use without requiring customer support.

Before Katalon Studio, I used Python Selenium for automation. It was challenging for people without a coding background to use. I managed to navigate it, but we had to install specific software for that. Katalon Studio, however, is easy; simply download the studio, and you can use it. That's why I switched to Katalon Studio without the worry of backend complexities.

Prior to selecting Katalon Studio, I considered automation tools such as Python Selenium. While Python was easier for me, Katalon Studio automation is much more user-friendly and accessible.

I started with the trial version and found it had many features. I purchased the next level, and the setup cost was reasonable for me. For working professionals, Katalon Studio provides a lot at a lower rate compared to others. Although there are free automation software options available, Katalon Studio offers everything in a single hub for a fee.

I have not seen a return on investment with Katalon Studio because it was my decision to start using it, and it is not used widely yet in the company. However, it may be more elaborately utilized in the coming years.

I have not seen a return on investment with Katalon Studio because it was my decision to start using it, and it is not used widely yet in the company. However, it may be more elaborately utilized in the coming years.

I started with the trial version and found it had many features. I purchased the next level, and the setup cost was reasonable for me. For working professionals, Katalon Studio provides a lot at a lower rate compared to others. Although there are free automation software options available, Katalon Studio offers everything in a single hub for a fee.

Prior to selecting Katalon Studio, I considered automation tools such as Python Selenium. While Python was easier for me, Katalon Studio automation is much more user-friendly and accessible.

My advice for others considering using Katalon Studio is to keep the software updated and optimize project settings for performance. Organizing tests and the object repository for maintainability is crucial. Specific tips include avoiding unreliable XPath indexes and managing Android permissions. Best practices also involve reducing startup time by changing Katalon Studio preferences to open a clean session and adjusting the default wait for element timeout to lower wait times. For grouped tests, use the test suite and test suite collection for better organization.

I would add some advanced thoughts on strategic adoption and planning. Align automation with business goals; don't automate just for the sake of it. Begin with a clear test automation plan that focuses on high-risk and high-impact areas. Foster a culture of quality, as test automation shouldn't be limited to the QA team. When all team members, including developers and product owners, understand and contribute to end-to-end testing, quality becomes a shared responsibility. Katalon Studio is very affordable, so every organization should consider using it because we need to move forward with technological advancements.

On a scale of 1-10, I rate Katalon Studio an 8 out of 10.

My main use case for Katalon Studio is automating test cases for both iOS and Android apps.

A specific example of a test case I automated with Katalon Studio is the lab test booking journey for our Tata 1mg Android and iOS apps, which help customers book lab tests and order medicines online.

The best features that Katalon Studio offers in my experience include reusability, which I find very valuable, and the XPath finders. The modification of test cases is very easy when compared to the traditional framework, which is the main advantage of Katalon Studio.

Reusability and the XPath finder have helped me significantly because there were cases with my current traditional frameworks where I struggled to find an XPath. In Katalon Studio, if you load the app, element finding becomes very easy. Additionally, if I want to change test cases, such as adding or removing any step, the process is straightforward.

The debugging process is also simpler. If any test cases fail using my current traditional framework, it was very difficult, whereas in Katalon Studio, I have debugged the failure test cases easily. With these features, I can save a lot of time using Katalon Studio compared to my current Java Selenium framework.

Katalon Studio has positively impacted my organization because I have noticed that I can save more than 50% of our time automating test cases. I measured this time saving by comparing the automation of cases in my current framework with automating the same cases through Katalon Studio using the record and playback method.

I have noticed a little lag while loading applications during my automation process with Katalon Studio, and I'm not sure if that is due to the free user restrictions, but I think this lag in application loading can be improved.

Katalon Studio sometimes restarts during automation, and as mentioned earlier, the app experiences lag, so those are the main areas that need improvement.

I have been using Katalon Studio for around one month because I was working to automate our 1mg app for my own interest.

In my experience, Katalon Studio is stable, but sometimes I encounter lag and crash issues. For instance, Katalon Studio was restarting two or three times when I was working with it, and I also found some lags while loading my app.

Katalon Studio handles larger projects and more complex test cases very easily, which is much simpler compared to my traditional framework.

I have interacted with the customer support team of Katalon Studio only once, and the support was very helpful and quick. Within 24 hours, I received support from the customer support team through their forum.

Previously, we used a traditional framework with Java, Selenium, and TestNG framework, and also tried Test Sigma. However, I found Katalon Studio very useful compared to all of these, and it saves a lot of time.

Before choosing Katalon Studio, I considered other options such as Test Sigma, which I tried in the same way as Katalon Studio.

I would rate Katalon Studio an eight out of ten. I chose this rating because I registered as a free user, and possibly due to that, I encountered those lags. If those issues had been resolved, I would have given it a 9.5 or 10.

My advice for others looking into using Katalon Studio is to consider that the industry is growing with no-code or low-code automation tools. In that case, Katalon Studio is very effective and saves a lot of time compared to others such as Test Sigma or TestTrio. It also has features such as optimized XPath finders that others do not offer, making Katalon Studio very advantageous when compared to other tools.