Specify iteration names in data-driven testing reports
When a test case is executed with a test data row, it is counted as an iteration. This document shows you how to differentiate iterations in test reports.
- This feature is available for data-driven tests with test suites. The changes only apply in the test suite HTML reports and the Test Case Table.
- To learn more about data-driven tests, see Data-driven Testing with Katalon Studio.
When working with data-driven tests, to quickly identify failed data inputs and parts of the application under test (AUT) that might have a problem, you can add a specific variable from the data file at the end of each iteration name. With this input for iteration name or iteration names, you can differentiate between each iteration in your data-driven testing reports at a glance.
Set iteration names in data binding
To set iteration names using one of the variables in the test data, do as follows:
- Perform data-binding from internal data, Excel, CSV, or database data. To learn more about data binding, see Run Test Case with an external data source.
In the Variable binding section, click on the Select toggle next to Set Test Name.
A list of variables appears. Choose an option to add to your iteration name.
Save and run your test.
View data-driven testing reports
After you set iteration names in data binding, in the Test Case Table and the HTML report, you can see your iteration names are tagged with the chosen variable in the following formula: ”Test case name”/”Iteration name” (“Elapsed time“)
.
-
In the Test Case Table:
To learn more about Test Case Table and reports, see Test Suite and Test Suite Collection Reports.
-
In the HTML report:
To learn how to export reports to HTML and other formats, see Export reports to other formats.