Viewing Test Suite Reports in Katalon Studio
Viewing Test Suite Reports in Katalon Studio
Learn about test suite reports and related functions in Katalon Studio, a testing platform allowing you to monitor your test status.
Join the DZone community and get the full member experience.
Join For FreeLearn more about how CareerBuilder was able to resolve customer issues 5x faster by using Scalyr, the fastest log management tool on the market.
Katalon Studio is designed to ease many challenges that manual testers are facing. In a large project, there may be hundreds or even thousands of test cases and test executions. Test suite reports produced by Katalon Studio allow users to monitor their test status and have a better understanding of their project’s test coverage. This guide will give you an overview of reports and related supported basic functions.
Once a test suite finishes its execution, a historical report is automatically generated and stored in the Reports section of Tests Explorer. Test suite execution reports are placed in chronological order with the most recent one on top.
For example:
The report will be named with following the naming convention: YYYYMMDD_HHmmss, which is the date and time when the test suite starts its execution.
Report Overview
In the Test Explorer view, double-click on a historical execution of a test suite to view its details:
where:
| Component | Description |
| Test Cases Table | List of executed test cases. |
| Summary | Summary information of executed environment. |
| Execution Settings | Settings for execution which include information about how to handle a failed test case, page loading timeout, etc. For example:
|
| Execution Environment | Information concerning the execution environment, including Host Name, Operating System (os), Katalon Studio version, browser, etc. For example:
|
Test Cases List
- The Test Case Table displays the list of all executed test cases in a test suite. If data-driven testing is used, each test case will be executed through a number of times (iterations) that are defined in the Data Iteration column of the current test suite as shown in steps No. 5 to 7 below.
Users can easily determine what information to display by using the filters.
| Filter | Description |
|
Show only iterations which are passed. |
 Failed |
Show only iterations which are failed. |
 Error |
Show only iterations having errors. |
 Incomplete |
Show only incomplete iterations |
Passed- By selecting an iteration in Test Case Table and click Show Test Case Details, you can view details regarding its executed logs.
- If qTest and JIRA are configured in Project Settings, you can submit the results to these systems. Refer to qTest Integration and JIRA Integration for more details.
Test Suite Summary
This section explains the information on the test execution summary report for a test suite, as shown below.
The fields include:
| Field | Description |
| Test Suite ID | The ID of the executed test suite in Katalon Studio. Once clicked, the test suite is opened. |
| Hostname / OS / Platform | The environment where the test suite is executed |
| Start / End / Elapse | Execution start/end date time and duration |
| Total TC | The total number of test cases, grouped into four status groups, Passed, Failed, Error, and Incomplete. |
Test Case’s Log
Test Case’s Log shows the detail of a test case after execution. Users can view such details in three tabs Test Log, Information, and Integration. Double-click on a test case in Test Cases Table to display the Test Case’s Log window.
Test Log Tab
- Details of the executed steps and their status are displayed in this tab.
Detail of the items:
| Component | Description |
| Log Information | Information of the selected iteration in the Test Case’s Log section:
|
| Log Image | The screenshot taken from the application under test, it is captured in either of the following situations:
|
- Users can easily determine which type of information to be displayed by using the provided filters:
| Filter | Description |
 Info |
Show the messages logged for information/reference. |
 Passed |
Show the steps which are successfully executed. |
 Failed |
Show the steps which failed to execute. |
 Error |
Show the steps having errors. |
 Incomplete |
Show incomplete steps. |
 Warning |
Show the steps which have warning status. |
 Not Run |
Show the skipped steps. |
- If JIRA is configured in Project Settings, users can submit a ticket to this system. Refer to JIRA Integration for more details.
- Screenshots are taken for the failed steps and users can hover the mouse cursor over the attachment icon to review.
Information Tab
Users can find the summary information of the test case in this tab.
The items include:
| Field | Description |
| Test Case ID | The ID of the executed test case in Katalon Studio. Once clicked, the system navigates users to the respective test case. |
| Start / End / Elapse | Execution start/end date time and duration. |
| Description | Description of the test case. |
| Message | Any system message raised when this iteration is executed. |
Integration Tab
The information regarding qTest Integration of this iteration is displayed in this tab.
The fields include:
| Field | Description |
| Test Log ID | The ID of the integrated qTest Test Run. Once clicked, the system navigates users to the respective qTest page. |
| Test Run Alias | The alias of the integrated qTest Test Run. |
| Attachment | Indicate whether all execution logs and reports are placed in a zipped file to be sent to qTest as an attachment. |
Export to Other Formats
For the purpose of sharing, users can generate reports of test suites into other formats such as HTML, CSV, PDF, and JUnit using the context menu in Test Explorer as the example below:
Katalon Studio’s Reports feature allows users to have an overview of test execution by providing most important details and necessary information from PASSED/FAILED result to details on the execution environment, test summary, or logs. Using this information, test managers and QAs can better manage and track test activities, resulting in improved testing productivity.
Stay tuned and keep exploring Katalon Studio with the Resources Center!
Find out more about how Scalyr built a proprietary database that does not use text indexing for their log management tool.
Like This Article? Read More From DZone
Published at DZone with permission of Oliver Howard . See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}