Skip to main content

Manage dynamic test suites in Katalon Studio

Last updated: October 2026

A dynamic test suite (DTS) is a test suite with multiple test cases added via a search query. You can dynamically add test cases based on the ID, name, tag, comment, and description of a test case.

This article shows you how to create and query test cases for execution in a dynamic test suite.

Create a new dynamic test suite​

To create a new dynamic test suite, do as follows:

  1. In the Tests Explorer panel, right-click at the Test Suites folder > New > Dynamic Test Suite.
  2. Fill in the name and the description (optional).
  3. Click OK.

You have successfully created a new dynamic test suite.

Add test cases to a dynamic test suite​

Use Built-in Search to add test cases that match your search criteria to a dynamic test suite. Build a query with Query Builder, or enter conditions directly in the Query box using AND and OR, as described in the next section.

  1. To search by tag, add tags in each test case's Properties tab and save the changes.
  2. Open a dynamic test suite and select Built-in Search under Query Provider.
  3. Click Query Builder and enter search criteria using Id, Name, Tag, Comment, or Description.
  4. Click Search to find matching test cases. Only test cases are added to the dynamic test suite.

Built-in search with AND - OR conditions​

From Katalon Studio version 11.6.0, Built-in Search supports AND, OR, and parentheses for grouping search conditions. Enter these queries directly in the Query box; the Query Builder dialog does not generate them.

Write each condition as keyword=value. Parentheses around the value are optional for a single word (tag=Sanity and tag=(Sanity) are equivalent), but required for values containing spaces or commas, such as id=(Test Cases/Checkout) or tag=(SSN, Sanity).

QueryTest cases that match
tag=SSN AND tag=SanityHave both SSN and Sanity tags.
tag=SSN OR tag=SanityHave SSN, Sanity, or both tags.
tag=(SSN, Sanity)Have both tags, equivalent to tag=SSN AND tag=Sanity.
(tag=Smoke OR tag=Sanity) AND tag=LoginHave Login and at least one of Smoke or Sanity.
id=(Test Cases/Checkout) AND tag=RegressionAre in the Test Cases/Checkout folder and have the Regression tag.
name=(Login) OR name=(Logout)Have Login or Logout in the name.

When combining conditions:

  • AND takes precedence over OR: tag=A OR tag=B AND tag=C is equivalent to tag=A OR (tag=B AND tag=C). Use parentheses around conditions to change the order.
  • Conditions without an operator between them use AND: tag=A tag=B is equivalent to tag=A AND tag=B.
  • Operators and tag names are case-insensitive. tag and tags are equivalent, and tag order does not affect matching.
  • Katalon Studio ignores conditions with an unknown keyword.
  • Queries with more than 50 opening parentheses are not run and return no matches.
note

From version 11.6.0, tag conditions match full tag names rather than partial text. For example, tag=(Log) no longer matches a test case tagged only with Login. Review queries that rely on partial tag matching when upgrading.

Modify execution information​

Before executing a test suite or a dynamic test suite, you might want to modify the execution information, including timeout, retry, and email recipient list for test execution reports.

You can specify additional configurations for the test suite execution by expanding the Execution Information section as below:

Execution Information section

Set implicit timeout in a test suite execution​

In Implicit timeout, you can decide the timeout period that Katalon Studio waits for a page to be loaded by choosing one of the following options:

Implicit timeout options
  • Use default: Use the predefined default value in Project Settings > Execution > Default wait for element to timeout (in seconds).
  • User define: Set a custom waiting time. Input a value in seconds.

Retry after executing all​

Katalon allows you to rerun test cases in a failed test suite execution to identify flaky tests.

To do so, in the Retry after executing all text field, set the desired number of retry times. By default, this is set to 0.

Retry after executing all options

Choose one of the following options:

  • Retry all executions: Retry all test cases when the test suite fails.

  • Retry failed executions only: Retry only failed test cases when the test suite fails.

    For example, when a test suite execution fails, we want to rerun failed test cases in that test suite twice.

    In the Retry after executing all checkbox, we input 2 in the text field, then we choose the Retry failed executions only option.

    Retry failed executions only option

In this case, the test suite is executed three times in total. The first one is the main execution, while the latter two are the retried executions when the first execution fails.

Test suite retry progress

Katalon Studio automatically generates reports after each test execution.

Test execution retry reports

Execute a test suite​

To execute a test suite or a dynamic test suite, follow these steps:

  1. In Tests Explorer, open a test suite or a dynamic test suite.

  2. Click on the drop-down of Run and select an environment to execute the test suite.

    Run drop-down with execution environments

    If you only click on Run, Katalon Studio executes the test suite with the default execution environment defined in Project Settings > Execution > Default execution. See Execution settings in Katalon Studio.

  3. Click Run.

The Job Progress is triggered automatically to show the progress while your test suite is being executed.

Job progress

You can also run a test suite or a dynamic test suite in console mode. For detailed instructions on test execution in console mode, you can refer to this document: Command-line syntax in Katalon Runtime Engine.

Was this page helpful?