Parallel test case execution

Last updated: September 2026

Requirements & Availability

Make sure you have the Test Lead or Tester role. Refer to this document for more details: Project level roles.

• This feature is only available for automated test run configured with Test Execution - Cloud environments.
• Applies to Test Suites (TS) and Test Suite Collections (TSC). Currently not supported for dynamic test suite.

Introduction

Parallel Test Case Execution speeds up your test runs by executing multiple test cases at the same time.

Instead of running test cases one after another, Test Execution - Cloud splits them across available sessions and completes your test suite faster.

Test Execution - Cloud optimizes resource use while keeping a buffer of sessions available. For example, you have 10 test suites, each with 10 test cases. Test Execution - Cloud continuously analyzes the queue and distributes test cases across the available licenses until all are used.

Katalon already provides execution modes in a Test Suite Collection (TSC), which determine how test suites are executed. Parallel Test Case Execution is distinct because it operates at the test case level, not just at the suite level. The following table highlights the key differences.

Mode	Scope	Description
Parallel Test Case Execution	Test Suite	Runs individual test cases in parallel within a suite or across suites, filling all available sessions. Offers maximum speed and efficiency.
Sequential (TSC)	Test Suite Collection	Runs one test suite after another.
Parallel (TSC)	Test Suite Collection	Runs multiple test suites in parallel, limited by your available Test Execution - Cloud session quota.

View available sessions

You can view your Test Execution - Cloud sessions by visiting the Test Execution - Cloud Web App home page. The dashboard displays:

• The number of sessions purchased for each session type (Desktop Browser, Mobile Browser, Mobile Native App).
• The number of sessions currently running.
• The number of sessions currently queued.

Enable parallel test case execution

1. Go to Executions. The Executions list appears by default.
2. Click + Create > Create Automated Test Run. The Create Automated Test Run page appears.

3. Input the following details:

• Test Run Name: The name of the test run
• Release Version (optional): The associated release
• Sprint (optional): The associated sprint

4. Click Select Tests to select from the list of test suites, then click Save when you’re done.

5. Enable the Parallelize Test Cases toggle.

6. Click the settings icon of each test suite to configure Test Execution - Cloud environment.

note

• For standalone test suites, you can configure multiple environments. However, if a test suite is part of a test suite collection, you can assign only one environment per test suite.

7. In the Select Configurations dialog, open the tab for the environment you want this suite to run in. Each suite can use a different environment, so one run can mix browser and mobile device sessions:

• On the Desktop & Mobile Browser tab, select Cloud Hosted, then specify the OS, browser and browser version.
• On the Mobile Native App tab, select a mobile app first, then specify the device configuration.
• On the Web Services tab, the fixed default configuration TestCloud Linux is used; it is not editable.

8. In the Automated Test Run page, click Run Now to execute instantly or Schedule to create a recurring schedule for it.

Best practices

Refer to the following recommendations to optimize your use of Parallel Test Case Execution.

• Your Account should have at least 3 available Test Execution - Cloud licenses per session type for optimal efficiency.
• Parallelize Test Cases also works on a run whose suites mix environments (for example, a desktop browser suite and a mobile native app suite in one run): the platform allocates both browser and device sessions in the same run.
• To utilize available sessions, schedule runs across different environments (for example, Desktop Browser and Mobile Native App). Avoid scheduling two test runs that use the same session type with Parallelize Test Cases enabled, as only one can execute at a time.
• Test cases must be independent. If the second test case requires data created by the first test case, the test run might fail when running in test case level parallel mode.