Systems | Development | Analytics | API | Testing

"Manual tester" lands differently depending on who's wearing the title, and both reactions are usually right. Ask someone stuck clicking through the same regression suite every release, no ownership, no say in what gets tested, and "manual tester" feels like a job you're trying to escape. Ask someone who can look at a new feature and instantly spot the edge case nobody thought to script, and the same title undersells what they actually do. Same word. Two different jobs.

Ask most QA teams how many tools it takes to manage one release and the list runs long: a repository for test cases, a separate grid for automated runs, a dashboard bolted on for reporting, and now an AI tool for generating or maintaining tests. Each has its own login, its own contract, and its own way of describing the same test case. That fragmentation is why "all-in-one test management platform" became the phrase buyers actually search for.

Before every session, I used to type some version of this: Sixty-two words of setup, and all of it gone the moment I closed the window. Here is the same request in week two, after the assistant had learned how my project works: That is the whole feature. Everything below is how it works and what I learned building it. THE SHORT ANSWER.

Katalon Studio 11.5.0 is available for all users as of August 27, 2026. This release focuses on richer reporting, AI assistance that reaches further into test authoring, a stronger mobile recording experience, a refreshed UI, and the performance problems that showed up in large projects. Here's what shipped, starting with the new features.

Most QA teams do not use one automation framework. They use two or three. Selenium handles the legacy suite and cross-browser regression. Playwright covers the newer end-to-end flows. Cypress runs the frontend component tests that developers wrote. Maybe there is an Appium layer for mobile. Each framework was adopted for a good reason. Each solves a real problem. But the result is fragmented visibility. Test results live in separate CI jobs. Reporting requires pulling data from multiple sources.

August was a month of giving teams more control over their own workspace, more room to trust what they automate, and a quieter but real security and reliability pass underneath it. Test cases get a real version history instead of silent overwrites. Project admins get to clean up their own taxonomy instead of filing a ticket. Playwright finally reaches the private networks the rest of the platform already could, and a critical vulnerability in the Katalon Agent gets patched along the way.

Every testing vendor says "AI-powered" now. Fewer of them can show you the actual verification pipeline underneath that claim: what gets checked, what gets trusted without checking, and what happens the moment something breaks. This is that pipeline, as I run it against True Production Insights, formerly known as TrueTest, every time we ship a change to it.

Playwright has gone from a browser automation library most QA teams had never heard of to one of the most-searched testing frameworks in the industry, and interest keeps climbing. If you're evaluating it for your team, comparing it to Selenium or Cypress, or just trying to understand what the interest is about, this guide covers the fundamentals: what Playwright actually is, how it works, what it's used for, and where to go next once you're ready to dig into best practices. THE SHORT ANSWER.

Playwright makes it easy to get a test running quickly. It's harder to keep a whole suite of Playwright tests reliable six months later, once your app has changed, your team has grown, and nobody quite remembers why a particular test is flaky three days a week. If you're new to Playwright, our guide to what Playwright is and how it works is a good place to start first.

Katalon's library of testing skills for AI agents holds 13 skills. Building it produces 124 files. The 13 skills are the actual work: how to plan a test cycle, how to design cases from a requirement, how to read a failing run and decide whether a release is safe. The other 111 files are packaging. Four of them arrived this month and they are the subject of this post.