Describe a web test in plain English or record it in the browser. Studio writes the steps and objects, you review them, and the same test runs on every major browser and in your CI.
Solutions · Web testing/shoplnk_jacketbtn_addToCartbtn_guestCheckoutlbl_orderStatus
Katalon Test Cloudkatalonc -testSuitePath="Test Suites/Checkout"Running checkout suite… All checks passed
Web testing checks that a web application works, displays correctly, and behaves the same across browsers before your users find the problems. Most teams automate four kinds of checks, and Studio handles all four in one project.
Check that sign-in, search, checkout, and every other flow still work after each change, then rerun the full set before a release.
Web application testingRun the same test on Chrome, Firefox, Safari, and Edge, because layout and behavior differ between browser engines.
Cross-browser testingVerify text, element state, and layout on the page the user actually sees, not only the markup underneath.
Automated web testingCheck the requests a page depends on in the same project, so a failing endpoint shows up before the page breaks.
API testingPick the way that suits the test and the person writing it. All three produce ordinary Studio test cases, objects, and scripts, so anyone on the team can pick up the result.
In Agent mode, Katalon AI Assistant (Kai) uses your project context to create the test case, run it, and troubleshoot it when a step fails. Every file change is shown for you to review before you keep it.
GA since Studio 10.3.2 · default mode since 11.1.2
Type the scenario in plain English and Studio runs each step live in the browser, saving regular test steps and objects. Prefer to drive? Switch to manual recording and click through the flow yourself.
AI recording: Beta since Studio 11.0.0 · paid plans
Build tests from built-in web keywords, switch to the script view for Groovy or Java, or work in BDD. Through the Studio MCP Server, your AI coding agent can write Gherkin feature files and their step definitions for you to review.
BDD authoring through the Studio MCP Server: GA since Studio 11.7.0 · paid plans
Tests created with AI can be tagged as AI-generated, so reviewers know which ones to check first.
Write web tests with AI or by hand, keep them passing as the UI changes, and run them on every major browser and in your CI.
btn_signIn Set text txt_email Verify text 'Welcome back'Describe the test in plain English and Studio records it step by step in Web Recorder Plus, saving test steps and objects you can edit. Or record it yourself.
Point Katalon AI Assistant at a Jira ticket or describe the requirement. In Agent mode it creates the test in your project and shows the file changes for review.
Your AI coding agent writes Gherkin feature files and their step definitions in your Studio project through the Studio MCP Server. You review and refine the code.
Objects are captured with ranked locators and fallbacks, so a renamed class or a moved button does not fail the test.
Before each web step, Studio waits until the page has loaded and the element is visible, still and editable, so timing failures drop without hard-coded sleeps.
When a locator breaks mid-run, Studio finds the element another way and logs what it changed, so you approve the fix instead of rerunning the suite.
Run the same suite on Chrome, Firefox, Safari and Edge at once on Katalon Test Cloud, with no grid or browser farm to maintain.
Trigger suites from Jenkins, GitHub Actions, Azure DevOps or GitLab with Katalon Runtime Engine. CI runs need a Runtime Engine license.
WebUI keywords were not recognised, so several scripts failed to compile. Two booking tests then ran with no browser open.
When a web run fails, AI reads the log, names the root cause in plain language and suggests a fix for you to approve.
AI is optional. Admins can turn AI features on or off for the organization and route supported AI requests through your own provider keys. Smart Wait and classic self-healing use no AI.
Debug on your own machine, then hand the same suite to Katalon Runtime Engine in your pipeline or to Katalon Test Cloud for browsers at scale.
Katalon Runtime Engine runs Studio tests from the command line in any CI system, including Jenkins, GitHub Actions, Azure DevOps, and GitLab. Tests and data can stay behind your firewall.
Run the same suite on Chrome, Firefox, Safari, and Edge across Windows and macOS at once, with no grid or browser farm to maintain.
CI runs need a Katalon Runtime Engine license. Test Cloud is licensed separately, and test case-level parallel runs need Katalon Studio Enterprise. See pricing for current plans.
The objects, test data, and keywords you build for web tests carry over. Add mobile, API, and desktop tests to the same Studio project and run them from the same pipeline.
Record native, hybrid, and mobile web apps on iOS and Android, then run them on real devices in Katalon Test Cloud.
Mobile testing in Katalon StudioBuild REST, SOAP, and GraphQL tests next to your UI tests, and check the calls a page depends on in the same run.
API testing in Katalon StudioAutomate native Windows desktop applications with the same keywords, object repository, and reports you use for web tests.
Desktop testing in Katalon StudioTesters who don't code and engineers who do work in the same project, on the same tests.
Selenium under the hood. Studio runs on Selenium 4 with TestNG and JUnit bundled, so your WebDriver code and Selenium IDE projects come with you.
Keep your Selenium tests“Katalon made automation a reachable option! I really love how easy it makes the automation process, in addition to how easy to use and understand this program is.”
“Katalon has a very small learning curve, which allows manual testers to become cross-functional across automated and manual testing.”
Web testing checks that a web application works as intended for its users: that its flows, its UI, and the API calls behind it behave correctly across browsers. Teams automate the repeatable parts, such as regression and cross-browser checks, and keep exploratory and usability testing manual.
Yes. Describe the scenario to Katalon AI Assistant in Agent mode, or point it at a Jira ticket, and it creates the test case in your project and shows the file changes for you to review. In Web Recorder Plus, the AI Recording Agent (beta) records a test from a plain-English description.
AI recording is available on paid plans. Free users see an upgrade prompt when they open it. See katalon.com/pricing for current plan details.
Yes. Katalon Runtime Engine runs Studio tests from the command line in any CI system, including Jenkins, GitHub Actions, Azure DevOps, and GitLab. CI runs need a Runtime Engine license.
Yes. Studio is built on Selenium and bundles Selenium 4, TestNG, and JUnit, so there are no drivers or libraries to install. You can import Selenium IDE projects, bring WebDriver code into a Studio project, and call WebDriver directly from your own code.
Chrome, Firefox, Safari, and Edge, on your own machine or on Katalon Test Cloud across Windows and macOS.
No. Authorized admins can enable or disable AI features for the organization, and supported AI requests can be routed through organization-provided provider keys. Katalon does not use customer AI input or output to train foundation models for other customers.
Start a free trial, describe or record one flow from your own app, and run it on two browsers before you change anything else.
Rolling out web testing across several teams? Talk to an expert
studio-mcp
