View test suite and test suite collection reports in Katalon Studio

Last updated: August 2026

Test suite report

You can view reports directly inside each test suite page.

After executing a test suite, to see the test suite report, go to the Result tab. It contains a test cases table and three tabs: Summary, Execution Settings, and Execution Environment.

Test cases table

The summary information of all executed iterations done in the test suite is displayed here. Each time when a test case is executed with a test data row is considered an iteration.

Use the filters above the table to show only iterations with a specific status: Passed, Failed, Error, Incomplete, or Skipped.

Test suite summary

This section gives the summary information of the test suite:

• Test Suite ID: The ID of the executed test suite in Katalon Studio.
• Hostname:The hostname of the environment where the test suite was executed.
• Local OS: The operating system used to open Katalon Studio.
• Platform: The operating system, browser, and browser version used to execute the test.
• Start / End / Elapse: The execution start time, end time, and duration.
• Total TC: The total number of test cases and their execution status.

Test case log details

To view details of the executed logs, in the Test Case table, select an iteration and click Show Test Case Details. The panel that opens has three tabs.

Test Log: shows details regarding all the executed steps and their status are displayed in this tab.

Use the following filters to control which log entries are displayed

Filter	Description
Info	Shows messages logged for information or reference.
Passed	Shows successfully executed steps.
Failed	Shows steps that failed to execute.
Error	Shows steps with errors.
Incomplete	Shows incomplete steps caused by factors such as invalid syntax, power loss, or a disconnected network.
Warning	Shows steps with warning status.
Not Run	Shows skipped steps.

If you have configured Jira integration, you can submit a ticket to this system. For further details, you can refer to this document: Submit an issue to Jira.

Information tab: shows the iteration-level summary.

• Test Case ID: The ID of the executed test case

• Start / End / Elapse: The execution start time, end time, and duration

• Description: The description of the test case

• Message: Any system message raised when this iteration was executed

  

Integration: shows qTest or Jira integration details for this iteration.

Test suite collection report

After executing a test suite collection, to see the test suite collection report, go to the Result tab.

Field	Description
ID	The ID of the executed test suite in Katalon Studio.
Environment	The environment in which the test suite was executed.
Status	Whether the execution is complete.
Failed Tests / Total	The total number of test cases and the number of failed test cases, if any.
Test Suite Details	Opens the test suite report.

Report history

Once a test suite/test suite collection finishes its execution, a report is automatically generated and stored in the Reports folder.

For example:

The report is named with the following naming convention: YYYYMMDD_HHmmss, corresponding to the date and time of the start of the execution.

Report settings

Go to Project > Settings > Report to open the report settings screen.

Automatically generate reports

This feature enables auto-generation of reports in the selected format.

Select your preferred format/s for the reports generated after each test suite execution. You can select at least one of the following available formats:

Format details

• HTML (.html) - Provides a comprehensive, browser-viewable summary of test results.
• CSV (.csv) - Spreadsheet-friendly format ideal for data analysis and integration with other tools. This is useful for creating custom dashboards or importing into reporting systems (e.g., Excel, BI tools).
• PDF (.pdf) - Printable, static snapshot of the test execution summary, which is ideal for sharing with stakeholders or archiving formal testing evidence.
• Console logs (console0.log) - Captures raw execution logs output by Katalon Studio during runtime and is useful for debugging, error tracing, and detailed execution review. When the primary log file exceeds the configured max size (e.g., 10 MB), additional files like console1.log, console2.log, and so on are generated.

note

• The CSV and PDF options are available for test suite reports only.
• When exporting test reports to PDF file, special characters will be converted to UTF-8 format.
• Starting from 10.4.0, AI Failure Analysis is included in HTML test reports. It provides instant, plain-language explanations for test failures. Learn how to enable and use this time-saving feature here: Katalon AI Assistant Failure Analysis.

HTML report file structure

The HTML report group controls which HTML report format Katalon Studio generates and how it optimizes the report's file size. It contains a Format section and a File size optimization section.

Format	Description
Standard report	Generates one HTML report per retry attempt of a test suite. This is the report structure Katalon Studio used in version 11.3.0 and earlier, and the format to attach when uploading results to third-party tools. Click View examples to see a sample report.
Consolidated report	Merges every retry attempt and every data-binding iteration of a test suite into a single HTML report. You get one file that shows the full execution story: which test cases were retried, how many attempts each one took, and the result of every data-driven iteration. Available from Katalon Studio 11.4.0. See Consolidated HTML report for more details.
Legacy	Generates one report per retry attempt using the report structure Katalon Studio used in version 10.2.0 and earlier.

Selecting HTML under Automatically generate these reports after test execution will also enable Standard report by default.

How the format options interact

• At least one of the report format must stay selected.
• Selecting Legacy clears and disables Standard report and Consolidated report (and its Generate a separate HTML report per test case child option), because the legacy report writer does not produce the entity execution data those two formats need.
• Selecting Standard report or Consolidated report disables Legacy, for the same reason.

File size optimization

• Link screenshots instead of embedding them: reduces report file size by saving screenshots as separate files instead of embedding them. See Link screenshots instead of embedding them.
• Split the report data into smaller files so large suites load faster: see Split report data into smaller files.

Consolidated HTML report

By default, Katalon Studio writes a separate HTML report for every retry attempt of a test suite, so a suite that retried twice produces three reports that you have to open one by one.

The option merges every retry attempt and every data-binding iteration of a test suite into a single HTML report.

note

If your project already used the consolidated report before upgrading, it keeps generating the consolidated report after you upgrade. To go back to one report per retry attempt, select Standard report instead.

Generate a separate HTML report per test case

When a test suite contains many test cases, a single test suite report can become long and slow to navigate, and it is hard to share the result of just one test case with a teammate.

The Generate a separate HTML report per test case option makes Katalon Studio write a standalone HTML report for each test case in the suite, in addition to the test suite report. Each test case report contains that test case's own steps, logs, and screenshots, and links back to the test suite report it belongs to. From the test suite report, you can open a test case report directly from the test cases table.

The test case reports are saved in the same execution folder as the test suite report, inside the project's Reports folder.

1. Under HTML report > Format, select Consolidated report. Generate a separate HTML report per test case is only available once Consolidated report is selected.
2. Select Generate a separate HTML report per test case.
3. Click Apply and Close.

note

• When this option is enabled, the Split the report data into smaller files so large suites load faster option is disabled, because the report data is already split into one file per test case.
• When sharing reports, zip the entire execution folder so the test suite report and all linked test case reports stay together.

Link screenshots instead of embedding them

When test executions are long or contain many screenshots, the report size may become too large, potentially causing issues when generating or viewing it.

Enable Link screenshots instead of embedding them, to reduce report file size to save screenshots as separate files in the Reports folder. The HTML report references these images through relative paths instead of embedding them.

Below is an example comparison of file sizes for an HTML report:

• Without the option, the report size is 271.7 MB with screenshots embedded.

  

• With the option enabled, the report size is reduced to 468 KB with screenshots linked.

  

note

When sharing reports, always zip the entire Reports folder to ensure all linked assets, such as images, are included.

Log file settings only affect the size and speed of log generation. They do not change the content of the logs and are intended for advanced users.

Split report data into smaller files

Enable Split the report data into smaller files so large suites load faster to improve the performance of large reports. This setting:

• Generates a lightweight overview HTML file containing test case summaries.
• Stores detailed results for each test case in separate .js files.
• Reduces memory usage and loading time.
• Keeps the report overview available even if some .js files are missing.

note

• In the HTML report, the Expand All button may not immediately expand all test cases if this option is enabled. Expand All works best in reports that are not split.
• When sharing the report, make sure to zip the entire report folder—including the HTML and .js files. Otherwise, detailed test steps are not displayed.
• Email reporting with this new format is not fully supported yet; only the summary is included in the email, not the full report.
• This option is unavailable when Generate a separate HTML report per test case is enabled, because each test case already has its own file.

PDF report template

From Project > Settings > Report, the PDF report template group lets you choose which PDF report engine Katalon Studio uses when PDF is selected under Automatically generate these reports after test execution:

Template	Description
New	The modernized PDF report template. Requires Enable New Execution Viewer in Execution settings.
Legacy	The PDF report structure Katalon Studio used in version 11.4.0 and earlier.

note

When Enable New Execution Viewer is turned off in Project > Settings > Execution, New is unavailable and Katalon Studio falls back to Legacy.

Additional report options

• AI failure reason analysis: Adds AI-generated failure explanations to HTML and PDF reports when Katalon AI Assistant is configured. This option is only available when the HTML report uses Standard report or Consolidated report (not Legacy), or the PDF report uses the New template.
• Auto generate report if execution is manually stopped: Generates a report when you manually stop an execution. See Generate reports when execution stops.

Manually export reports

For test suite collections, you can export to HTML format only.

To manually export reports, follow these steps:

1. Open the Result view of a test suite or a test suite collection.

2. In the upper-right corner, select Export report, then choose an export format.

attention

You may encounter errors when generating HTML reports with large sizes.

• Generating reports larger than 500 MB might cause the error java.lang.OutOfMemoryError: Java heap space, and PDF reports might not be generated.
• HTML reports larger than 512 MB might not be rendered and displayed well on a browser, however, the HTML report still includes full information about test execution.

The recommended size for HTML reports is 500 MB. For large executions, you might want to reduce the amount of screenshots taken, avoid taking full-page screenshots, or enable the Link screenshots instead of embedding them, to reduce report file size option.

Customize log file settings

Katalon Studio offers configurable system properties that let users manage how log files are generated, stored, and buffered. These settings are particularly useful for optimizing performance and storage during large-scale or long-running test executions by controlling log file size, retention limits, and buffering behavior.

By default, when the console0.txt file exceeds 10MB, Katalon Studio automatically splits the log into sequential files (e.g., console1.log, console2.log, etc.).

To customize this behavior, follow the steps below:

1. Open the katalon.ini file in a text editor.

2. Add the desired -D system properties below the -vmargs line.

For example:

-vmargs
-DmaxLogFileSize=5242880
-DmaxLogFile=100
-DlogRecordQueueSize=10000
-DbatchLogRecordSize=5000

Refer to the following table for system properties you can use to customize log behavior:

Property	Description	Default Value	Example Configuration
-DmaxLogFileSize	Sets the maximum size (in bytes) a log file can reach before a new one is created.	10MB	-DmaxLogFileSize=5242880 (5MB)
-DmaxLogFile	Defines the maximum number of log files to retain. Older logs are deleted beyond this limit.	2000	-DmaxLogFile=100
-DlogRecordQueueSize	Specifies the size of the queue that holds log records before they are processed.	7000	-DlogRecordQueueSize=10000
-DbatchLogRecordSize	Determines how many log records are processed in a single batch.	3000	-DbatchLogRecordSize=5000

See the following recommendations below for best practices:

• The first two properties (maxLogFileSize, maxLogFile) are the most commonly used. Adjust the queue and batch sizes only if needed for advanced troubleshooting.

• Only adjust -DlogRecordQueueSize and -DbatchLogRecordSize if you are troubleshooting log buffer warnings.

  tip

  You may encounter the following log warnings when adjusting -DlogRecordQueueSize and -DbatchLogRecordSize:

  The buffer of log file is full. The stdout line is dropped and won't be in the log file.
  The buffer of log file is full. The stderr line is dropped and won't be in the log file.

  To resolve this, increase the following values to:

  -DlogRecordQueueSize=10000
  -DbatchLogRecordSize=5000

• Restart Katalon Studio after applying any changes to katalon.ini.

Log Viewer

Execute a test suite and observe the Log Viewer after the test execution completes. The generated reports are the same as the settings you have configured above:

You can view the generated reports in <project_folder>\Reports\<execution_folder> after the test execution finishes.

• Test suite report folder:

  

• Test suite collection report folder:

  

Video capturing

note

• K-Lite Codec is recommended to play the Katalon Studio test execution videos. You can download K-Lite Codec on the Codec Guide website: K-Lite Codec.
• Support execution at the test suite level.
• Support all browsers except for Remote, Headless, Kobiton, and Custom. For remote or headless browsers, it's recommended to use Katalium Server to view captured sessions.
• Recording parallel execution is NOT supported yet.
• On Linux, videos recorded in Katalon Studio require VLC for playback, except for WebM files, which can be opened in most browsers.

Debugging can be time-consuming and challenging for many automation testers. Katalon Studio helps solve this problem by supporting you with the ability to capture test execution via video format. You can enable the video capturing feature in Project Settings.

To learn how to work with Katalon Studio’s video capturing feature, see:

• Generate browser-based videos in Katalon Studio reports
• Generate screen-based videos in Katalon Studio reports

After executing a test suite, go to the Result tab. The test cases table displays each test case along with its attached video.

To play the video, click the play icon in the Video column. Test step descriptions are embedded as subtitles:

By watching how the automated test was executed, the testing team can identify exactly where the test failed. Thus, time and resources are managed more efficiently and effectively.

Learn about test suite reports, exporting, and more in our Katalon Academy course: Katalon Studio: How To Work With Execution Logs and Test Reports.

See also: Get generated reports location at runtime