Data-driven testing in a test suite

Last updated: November 2026

Data-driven testing in a test suite lets the suite supply data to a test case. The test case defines variables, and the suite maps those variables to columns in a test data file. Katalon Studio then runs the test case with the selected data rows.

Use suite-level binding when a particular suite needs its own data or variable mapping for a test case. If the test case should keep the same binding wherever it runs, configure data-driven testing at the test case level instead.

info

Starting with Katalon Studio 11.7.0, data-driven test execution requires a paid plan. See pricing page.

How suite-level binding works

A test case might define employee, department, and position variables. A suite can bind them to three columns in a data file. Each selected row supplies a set of values for one iteration of that test case in the suite.

The binding belongs to the suite test case. Another suite can use the same test case with a different data file or mapping. In the suite editor, select Use Variables and Binding at Suite Test Case to use the suite's configuration. Select Use Variables and Binding at Test Case to use binding saved in the test case instead.

What you need

• A test case with variables for values that change between runs.
• An internal or external test data file with a column for each value you want to supply. If you use a database, configure its connection first.
• A test suite containing that test case.

The following example defines three variables in the test case. The suite supplies their values:

Perform data binding in test suite

Set up the binding manually

1. Create or import test data from File > New > Test Data. Define the variables in your test case, then add that test case to a test suite.
2. In the suite editor, click Show Data Binding, select the test case, and choose Use Variables and Binding at Test Suite.
3. In Test Data, click Add and select the data file. Choose the data rows to use for execution.
4. In Variable Binding, if variable names match column names in the selected data file, click Map All to set Type to Data Column and bind them.

   For unmatched variables, click Set Type > Data Column, then use Set Test Data to choose the file and Value > ... to choose each column.

5. Save and run the test suite. Check the Log Viewer and suite report for the result of each iteration.

The Value selector lets you choose the data column for a variable:

For more about the binding controls and relationships between multiple data files, see Manage data binding.

Use Katalon AI Assistant Agent mode

In Katalon Studio 11.6.0 and later, Katalon AI Assistant Agent mode can use the built-in Katalon Studio MCP tools to create test data and bind it to a suite entry. For a test case that already defines employee, department, and position variables, try this request:

Create internal test data `Data Files/Employees` with columns `employee`, `department`, and `position`. Add two rows: Sam, Support, Agent; and Alex, Sales, Manager. Add `Test Cases/EmployeeDetails` to `Test Suites/EmployeeDDT`. Bind the data file to that suite entry, mapping each variable to its same-named column. Use **Variables and Binding at Suite Test Case**. Show me the data and binding before running the suite.

Agent mode can use writeInternalTestData for the rows, writeTestSuite to add the test case, and bindTestDataForTestSuite for the suite entry's mapping. The binding tool updates an existing entry, so the test case must be in the suite first. If the test case still needs to be created, writeTestCase can define its script and variables. After reviewing the changes, you can ask Agent mode to run the suite with executeTest and retrieve the results with getTestExecutionResults.

Review the results

The Log Viewer shows each iteration of the test case. You can also review the suite report in Reports in Tests Explorer or the project's Reports folder. To give iterations descriptive names in suite results, see Specify iteration names in data-driven testing reports.