We’re bringing back the Ask Katalon Anything (AKA) Series 8 session for the community. Now in its 8th edition, Ask Katalon Anything has grown into a regular highlight of our community. After seeing strong participation in the past seven rounds, we’re continuing these open conversations quarterly, as a way for users to connect directly with Katalon Product Managers, ask questions, and learn from each other’s experiences.
This AKA will focus on two areas: Web Testing and TrueTest. It’s a chance to talk directly with Katalon product managers and engineers, ask about upcoming features, discuss testing strategies, or get help with an issue you’re facing.
Ask Katalon Anything will come back soon, from 2025-09-22T23:00:00Z to 2025-10-21T16:39:00Z. Location: right here on the Katalon Community
If you have questions you’d like answered, please post them in the thread below. We’ll review them before the session starts. We look forward to your input and hope to see you all here.
With recent version update, do product team notice about this issue and/or other performance issue related. looking forward about official response from product team about that
Does Katalon currently provide MCP (Model Context Protocol) for AI integration? If not, is there a plan to support this feature in the future, and if so, what is the estimated timeline?
Nice to e-meet you. The idea looks interesting, can you elaborate more about the PlayWright support in Katalon? For instance, what is the problem/use case, and what is the ideal PlayWright support you would want to see in Katalon?
This is an interesting question. The Flutter Web has a custom rendering engine that presents a significant challenge for automation engineers seeking to locate and interact with elements.
Katalon Studio has supported the Flutter-based web app since 10.0.1, which you can read from the doc below
There are some practices for your test code to work seamlessly with the Flutter web app, which are supported by the Studio
Flutter’s rendering can be dynamic. The absence of a traditional DOM can sometimes cause synchronization issues. You should use explicit waits to ensure elements are present and interactive before performing actions on them
You should use multiple locators for the element so that you can retry the finding with them when the element isn’t present.
Employ Page Object Model pattern (POM), which separates the test logic from the UI locators, making your code more readable, maintainable, and resilient to UI changes
If you have a particular problem, feel free to share it here so we can talk about the specifics
Hello! I’m thinking about using katalon recorder as an upstream branch, as our team has some specific needs that are not met by the current chrome extension. However, on the public katalon recorder git repo the last commit/release was long ago. According to the repository, the latest Version is 5.6.1 but the extensions Window says it’s version 7.1.0
Are you planning on releasing the Source Code of the latest version? And if so, when would that probably be?
Thank you very much!!
Hi @duy.lam
Nice to e-meet you.
As you know, Playwright is very popular because it is open source and developed by Microsoft.In particular, I can use Playwright MCP to automatically generate test scripts.
Although these features can also be achieved with AI in Katalon, in order to enable more people to join testing—not just dedicated QA personnel—the scenarios include:
Using MCP in VS Code to generate Playwright or Katalon test scripts.
Katalon being compatible with Playwright test scripts, either by directly supporting them or by automatically converting them. This way, the current practices can be continued.
