Katalon

As an admin, the centralized governance over projects, licenses, and execution environments in TestOps is the standout. I can see which scripts are running, who owns them, and which tests are consistently flaky, all in one place. For our automation engineers, the dual self-healing engine is a big deal, as the classic rule-based healing handles simple locator shifts, and when that fails, the LLM-backed AI self-healing kicks in using the page structure and accessibility tree context to recover the element. This layered approach is smart and practical.

The ability to record tests is useful, and the element library is handy. I can apply my front-end knowledge to update selectors and it's easy to create tests as a team an share them via a repo.

Support is readily available when needed

LLM-powered AI self-healing requires extra setup to connect to your own AI model, which is not obvious to new admins and the documentation is still catching up. Also, Katalon Studio releases updates frequently, which is great for features, but means our team gets nagged with upgrade prompts constantly, and some plugin dependencies break on minor version bumps. Tighter backward compatibility would reduce that friction significantly.

The product feels dated. It's been updated, but still comes across as an old product with a new skin.

The UI is not great, settings are scattered around the application (project > settings can be hard to navigate before you are familiar with it). I'm not a fan of the UI in general and I'd rather use the code instead, using the application only for specific tasks. Web drivers updates are also problematic, it mostly fails most of the time at least in my environment. I often need to update it manually whenever there is a release. This is not an issue if you are using their docker image