Katalon Studio + Runtime Engine · 5-minute guide
Build tests in Studio, then let them run every week on their own
What your package does, the 3 milestones that show its value, the 5 steps to reach them, and how to get help here on the forum.
1 · What your package does
Two products, one job: tests your team builds once and runs again and again.
Build
Katalon Studio
Record or describe tests in plain words. Katalon AI writes scripts and fixes broken steps.
Desktop app on each tester’s computer
Studio alone stops at the first box: tests run only while Studio is open on one computer. Runtime Engine removes that limit.
2 · Your 3 milestones
Each milestone is something your team can see. Reach all three and your tests run every week without anyone clicking Run.
3 · Reach them in 5 steps
About one step a week. Each step ends with something you can see.
1
Get your team in (M1)
Week 0 · Account Admin, testers
- Account Admin: invite testers in Account Settings > Org > User Management, and assign each one a Katalon Studio licence.
- Account Admin: check your Runtime Engine licence in License Management. The person or machine that runs tests will use it.
- Each tester downloads Katalon Studio and signs in with the same email to activate it.
You’ll see: every tester opens Studio with no licence warning.
2
Build your first test
Week 1 · Each tester
Pick one important flow, like login. Then choose how to create the test:
With AI: describe it to Katalon AI Assistant
Write what the test should do in plain words. The AI Assistant (formerly StudioAssist) writes the script.
Without AI: record it
Click through your app. Studio records each action. No code needed.
You’ll see: your own working test in Studio, ready to run.
3
Run it and read the report (M2)
Week 2 · Each tester
- Put your tests in a Test Suite, and run it in Studio.
- Open the report in Tests Explorer > Reports. It shows what passed, what failed and why.
- A step broke because the page changed? Turn on self-healing so Studio finds the element another way and suggests the fix.
You’ll see: every tester has a passing suite. That is milestone 2.
4
Run without opening Studio
Week 3 · Test lead
- Download Runtime Engine on the machine that will run your tests.
- In Studio, open Command Builder from the main toolbar. Pick your Test Suite and browser, then click Generate Command. Your Katalon API key is filled in for you.
- Paste the command into that machine’s terminal and run it.
You’ll see: your suite runs from one command, with nobody clicking in Studio.
5
Make it run every week (M3)
Week 4 · Test lead, DevOps
Put the same command where it runs by itself. Choose one:
With your pipeline: CI/CD
Tests run on every build or release. Ready samples for Jenkins, GitHub Actions, Azure DevOps, GitLab and more.
No pipeline yet: a schedule on your test machine
Save the command as a script and schedule it, for example every night, with your machine’s task scheduler.
Tip: add -retry=1 so a test that fails once is run again before it is reported.
You’ll see: tests running every week on their own. That is milestone 3.
4 · Get help on the forum
You can read the forum without an account. You need one to post.
JOIN
Set up your account
Sign up with your work email. Add a photo, your role and the products you use. Then reply below to say hello.
Tip: set the bell on a category to Watching to get updates.
Never post API keys, passwords or private company data. For account or billing issues, use the Support Portal.