Systems | Development | Analytics | API | Testing

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.

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.

Most test automation tools are sized for one kind of team. The ones a lean QA group can adopt inside a quarter tend to buckle when a compliance officer asks who approved a change and when. The ones large enterprises standardize on often need a dedicated platform team before anyone writes a single test. Anyone who has evaluated tooling knows the feeling of reading a glowing review and realizing it was written by someone at a company nothing like theirs.

July was an enterprise month. Most of what shipped answers the questions that come up once a test team grows past a handful of people: how do we hand documentation to an auditor, where is the evidence for this step, who changed this result and when, and how do we run the same suite against a feature branch without rebuilding the integration every time.

Claude Code shipped workflows: reusable, versioned instructions an agent can follow instead of improvising a process from scratch each time. We used that feature to hand Claude Code our entire QA job. Not "write a test case." The whole loop: read the requirement, design the coverage, run it on the platform, file the defect, report back with evidence. The kind of work a QE does in a day, compressed into one skill triggered with a sentence.