Katalon True Automation · 5-minute guide
Automated tests that run on their own, with results your whole team can see
What True Automation is, whether it fits you, and the 5 steps to see its value.
1 What it is
Three jobs, one package. Build tests, run them, and see results in one place.
Build
Katalon Studio
Record or describe tests in plain words. AI writes and fixes scripts.
Desktop app on each tester’s computer
Run · choose one or both
Katalon Runtime Engine
Runs tests on your own machines or CI/CD, even inside private networks.
OR
Katalon TestCloud
Runs tests on Katalon’s cloud browsers and real devices. Nothing to maintain.
Katalon Studio alone stops at the first box: tests run only while Studio is open on one computer.
2 Is it right for you?
Most teams know in 30 seconds. Tick the lines on the right that sound like you.
Katalon Studio is enough
One person, tests by hand
- One tester creates and runs the tests.
- Tests run when you click Run.
- Nobody else needs to see results.
Choose True Automation
A team that needs tests to run on their own
- Two or more people create, run or read tests.
- Tests should run nightly or on every release.
- Managers want results and trends in one place.
- You test many browsers or devices.
- Non-technical teammates should run tests in one click from a browser, with nothing to install or maintain.
Two or more ticks? True Automation will save your team time.
3 See the value in 5 steps
All five steps fit in your first week. Each step ends with something you can see. Mark each one as done as you go.
- Sign up for a free trial, or sign in with your work email if your company already has True Automation. Select your organization.
- Account Admin Create a project for your team. Test runs and results will live here.
- Account Admin Invite teammates in Account Settings > Org > User Management, and assign each tester a Katalon Studio and a True Platform license.
- Project Admin Add teammates to the project and set their project role.
- Each tester downloads Katalon Studio and signs in with the same email to activate it.
On a free trial, you hold both admin roles, so you can do steps 2–4 yourself.
You’ll see: every teammate opens the project, with no license warning.
Pick one important flow, like login. Then choose how to create the test:
Without AI
Record
Click through your app. Studio records each action. No code needed.
OR
With AI
Describe with StudioAssist
Write what the test should do in plain words. StudioAssist writes the script.
Then: put the test in a Test Suite, and run it in Studio until it passes.
You’ll see: a working test that passes, ready to share with your team.
In Studio, open Project > Settings > Katalon True Platform (Katalon TestOps), enable it, and run your Test Suite.
You’ll see: the result in your browser, ready for the whole team.
First: make your tests available in True Platform. Upload the project as a ZIP, or connect Git.
Then choose where your tests run:
No setup
TestCloud
Katalon’s cloud browsers and real mobile devices. Pick the OS and browser per run.
OR
Your own machine
Local Agent with Runtime Engine
Runs on a machine or VM you manage, inside your network. Best for private or offline apps.
Finally: create an automated test run with your Test Suite and set a schedule, for example every night.
You’ll see: tests running every night, without anyone’s laptop.
Right after your first runs: open the results and let Katalon AI explain any failures.
From week 2: check pass rate and flaky tests in Reports as trends build up, and check release readiness before each release.
You’ll see: less time on failures, and clear quality progress to share with stakeholders.
All 5 steps done. Nice work! Share what you set up, or what tripped you up, in a reply below.
Need help?
Support Assistant · instant how-to answers Support Portal · open a ticket Onboarding team · amelia@katalon.com
Or just reply to this topic and the community will help.
Based on Katalon Docs, October 2026: About True Platform · Connect Studio · Automated test runs
- Step 1: Get your team in
- Step 2: Build your first test
- Step 3: Send results to True Platform
- Step 4: Run tests on a schedule
- Step 5: Review results and improve
- Two or more people create, run or read tests
- Tests should run nightly or on every release
- Managers want results and trends in one place
- You test many browsers or devices
- Non-technical teammates should run tests from a browser