# Getting started with Katalon Studio and Runtime Engine: your first 4 weeks

**URL:** <https://forum.katalon.com/t/getting-started-with-katalon-studio-and-runtime-engine-your-first-4-weeks/195380>\
**Category:** Getting Started with Studio\
**Tags:** onboarding, kre, katalon-studio\
**Created:** [November 18, 2026, 6:38am UTC](https://forum.katalon.com/t/getting-started-with-katalon-studio-and-runtime-engine-your-first-4-weeks/195380 "2026-11-18T06:38:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nghi.phan](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/nghi.phan/32/30970_2.png) [@nghi.phan](https://forum.katalon.com/u/nghi.phan)\
**Post date:** [November 18, 2026, 6:38am UTC](https://forum.katalon.com/t/getting-started-with-katalon-studio-and-runtime-engine-your-first-4-weeks/195380/1 "2026-11-18T06:38:35Z")

</div>

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.

[Download Katalon Studio](https://katalon.com/download)

Desktop app on each tester’s computer

Run · without opening Studio

### Katalon Runtime Engine

Runs your Studio tests from the command line: in your CI/CD pipeline, on a schedule, or inside Docker.

[Download Runtime Engine](https://katalon.com/katalon-runtime-engine#kre_page)

See results

### Test reports

Every run writes a report: passed, failed and why, with screenshots.

In Studio, your CI tool, or exported as HTML

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.

MILESTONE 1

### Team ready

Testers have a Studio licence and have signed in.

**Why:** a licence nobody uses is a test nobody writes.

MILESTONE 2

### Every tester builds and runs tests

Each tester has created a test and run it in Studio.

**Why:** tests come from the whole team, not one person.

MILESTONE 3

### Tests run every week

Runtime Engine runs your suite in at least 3 of every 4 weeks.

**Why:** bugs are caught every week, not only before a release.

## 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

1. **Account Admin:** invite testers in _Account Settings \> Org \> User Management_, and assign each one a Katalon Studio licence.
2. **Account Admin:** check your Runtime Engine licence in _License Management_. The person or machine that runs tests will use it.
3. 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.

[Invite teammates & assign licenses](https://www.youtube.com/watch?v=H7107k05Ea0) [Download & activate Katalon Studio](https://www.youtube.com/watch?v=LKG48Z1LK6k) [Activate Studio and Runtime Engine licences](https://docs.katalon.com/katalon-studio/get-started/activate-licenses)

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.

[Write steps with AI](https://www.youtube.com/watch?v=7E5JE6b85Uc) [From a Jira ticket](https://www.youtube.com/watch?v=pvOVEEZHjY4) [From a text file](https://www.youtube.com/watch?v=640JmZMFyK8)

**Without AI: record it**

Click through your app. Studio records each action. No code needed.

[Record a web test](https://www.youtube.com/watch?v=FzTjW1ieB4M)

**You’ll see:** your own working test in Studio, ready to run.

3

### Run it and read the report (M2)

Week 2 · Each tester

1. Put your tests in a Test Suite, and run it in Studio.
2. Open the report in _Tests Explorer \> Reports_. It shows what passed, what failed and why.
3. 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.

[Create a Test Suite](https://www.youtube.com/watch?v=1XsexSpmssw) [Read test suite reports](https://docs.katalon.com/katalon-studio/test-reports/view-test-reports/view-test-suite-and-test-suite-collection-reports-in-katalon-studio) [Self-healing tests](https://docs.katalon.com/katalon-studio/maintain-tests/self-healing-tests-in-katalon-studio)

4

### Run without opening Studio

Week 3 · Test lead

1. Download Runtime Engine on the machine that will run your tests.
2. 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.
3. 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.

[Get started with Runtime Engine](https://docs.katalon.com/katalon-studio/execute-tests/katalon-runtime-engine/get-started-with-katalon-runtime-engine) [Command options](https://docs.katalon.com/katalon-studio/execute-tests/katalon-runtime-engine/command-line-syntax-in-katalon-runtime-engine)

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.

[CI/CD samples](https://docs.katalon.com/katalon-studio/integrations/cicd-integrations/cicd-integration-overview)

**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.

[Runtime Engine use cases](https://docs.katalon.com/katalon-studio/execute-tests/katalon-runtime-engine/katalon-runtime-engine-overview)

**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.

ASK

### Ask a good question

Search first. Then post in the right category (Web, API, Mobile or Desktop Testing; KRE and agents go under Katalon True). Include your version, OS, steps, what you expected, and the full error as code.

**Tip:** mark the reply that fixed it as **Solution**.

GIVE BACK

### Answer and earn Kudos

Answer questions you know, share what you built, and join Ask Katalon Anything sessions. Helpful answers earn Kudos points you can exchange for rewards.

**Rules:** Answer and Earn \> How To Join in the sidebar.

Never post API keys, passwords or private company data. For account or billing issues, use the Support Portal.

## Need help?

[**Support Assistant** · instant how-to answers](https://assistant.katalon.com/) [**Support Portal** · open a ticket](https://support.katalon.com/) [**Community forum** · ask other testers](https://forum.katalon.com/)
