Thank you very much for tuning in our recent webinar session with Ravikanth Edamakanti (@ravikanth.edamakanti0 and Sanket Dudhe (@sanket7843) !
We hope that through our speakers’ sharing and expertise, you’re now more informed on how to set realistic automation goals, gained useful automation strategies, and successfully familiarized yourself with essential Katalon features for a productive workflow.
Please find a recording of the webinar session below
We’ll be updating this thread with all the answers to your questions asked during the Q&A session. Stay tuned!
Thank you very much @viet.nguyen from the Academy team for putting this webinar together!
Q: I tried adding setup/teardown to my test cases in order to close the browser even in case of test case failure according to the advice in YouTube tutorials, but received error messages. Is there a workaround in case I cannot fix it and how bad is it if the browser isn’t closed in case of test case failure? Is it absolutely crucial to have a setup/teardown structure in place? Thank you.
A:
Great question! Having a setup/teardown structure is important because it ensures things like the browser are closed properly, even if a test fails. If the browser isn’t closed, it can cause issues like using up system memory or interfering with other tests. While it’s not critical for small tests, it can become a big problem if you’re running many tests or using a continuous integration system.
To ensure the browser closes even if a test fails, use a Test Listener in Katalon. Add this in your listener:
Q: Hi, can Katalon Studio be used to check if a website has good accessibility? Any good resources on Katalon website/academy for that?
A:
Hi there, Katalon Studio can indeed be used to check a website’s accessibility through its integration with the Axe-core library and the Katalon Accessibility Test Plugin. This allows you to automate accessibility testing, ensuring compliance with standards like the Web Content Accessibility Guidelines (WCAG).
Q: Hi, I’d like to know if the Katalon Studio Free version (KS Free) supports creating test cases, playing them back, creating test suites, and exporting test reports.
A:
Yes, Katalon Studio Free version (KS Free) supports the following features:
Creating Test Cases: You can create automated test cases using record and playback.
Playing Back Test Cases: The free version allows you to execute recorded test cases.
Creating Test Suites: You can organize test cases into test suites for structured testing.
Exporting Test Reports: You can export test reports for analysis and sharing.
Overall, KS Free is a robust option for getting started with automation testing.
You can download Katalon Free by heading to the link below:
Yes, Katalon Studio provides several ways to export test results. After executing your tests, you can export test reports in various formats, including CSV(Detailed & Summary View), PDF, and HTML, directly from the test suite report options.
Please refer to the documentation below for more information:
Q: Hi, can a SQLite database be used for test data?
A:
Yes, a SQLite database can be used for test data in Katalon Studio. You can establish a connection to the SQLite database using JDBC and execute queries to fetch or manipulate test data.
For example, you might create a custom keyword to connect to the SQLite database and execute a SQL query like this:
Q: Could the script record from a desktop browser can be run in a mobile browser (for example the Safari browser on an iPhone)?
A:
Yes, scripts recorded in Katalon Studio from a desktop browser can be run on mobile browsers, including Safari on iPhone. This is possible through Katalon’s integration with cloud testing services like BrowserStack and LambdaTest, which allow for executing tests on real mobile devices. You can also use Katalon TestCloud for mobile browser executions.
Please refer to the documentations below for more information:
Q: Is it necessary to create a framework for every project?
A:
While it is not strictly necessary to create a comprehensive framework for every project in Katalon Studio, establishing some level of structure is beneficial. Katalon Studio already provides a built-in framework that users can leverage without any extra effort, which simplifies the process of test automation.
This well-structured framework offers a systematic approach, ensuring consistency and efficiency across projects. It facilitates the organization of test cases, management of test data, and reusability of scripts, ultimately saving significant time and effort in the long run. For smaller or simpler projects, a lighter approach may suffice, but a robust framework is essential for scalability and maintainability.
Q: Does the Record and Play feature always work reliably or are there limitations to consider?
A:
The record and play feature in Katalon Studio is an incredibly powerful tool that allows users to quickly generate automated test scripts with ease. It simplifies the automation process, enabling even those with minimal programming experience to create effective test cases effortlessly. While it’s true that if the user interface (UI) elements change, modifications to the recorded scripts may be necessary, this is a common aspect of any automation tool.
You can further check out this article on some of the best practices to use this feature:
Q: For someone just starting out with test automation, could you provide a specific example of a quick win or a simple task they can successfully automate early in their journey?
And, can you share how achieving this help would help to build confidence and set a strong foundation for more advanced automation projects?
A:
Hi there, a great quick win for beginners in Katalon Studio is automating simple scenarios like the login functionality of a web application. This task typically involves navigating to the login page, entering valid credentials to verify that users can log in successfully, and testing invalid credentials to ensure that appropriate error messages are displayed. Successfully automating simple scenarios or functions can significantly boost a beginner’s confidence by demonstrating the immediate benefits of test automation.
Moreover, it helps establish foundational skills such as object identification and assertions, which are crucial for progressing to more complex automation projects.
Q: Beginners often struggle with setting realistic goals when starting with test automation, which can lead to frustration or burnout. Could you discuss some of the most common mistakes that beginners make in this process, such as overestimating what can be automated or focusing on the wrong priorities?
Additionally, what practical strategies or tips would you suggest to help them avoid these pitfalls and maintain both motivation and consistency in their automation journey?
A:
Beginners in test automation often face challenges in setting realistic goals, which can lead to frustration or burnout.
Common mistakes include overestimating what can be automated right away and focusing on less critical tests instead of high-impact areas that would yield greater benefits. Additionally, many newcomers overlook the maintenance required for automated tests, leading to disillusionment when scripts fail due to changes in the application.
To avoid these pitfalls, beginners should start small by identifying high-value tests that are repetitive or prone to human error for automation.
Last but not least, you can check out our documentations for information on setting up and integrating Katalon with other tools, alongside how to make the most out of Studio’s essential features: