Viewing the execution log is the very first approach when troubleshooting automation test execution. The critical information in the log can quickly help project teams pinpoint the root causes of any issues. Katalon Studio execution logs are optimized to provide such information so that you can have a comprehensive view of the tests run.
View Execution Log
Once your test cases/test suites finish execution, you can review the results on the Log Viewer views.
Using the filter options, you can specify what type of logs to be displayed:
|All||Show all the log messages.|
|Info||Show only the log messages for information/reference.|
|Passed||Show only the log messages indicating that a step is successfully executed.|
|Failed||Show only the log messages indicating that a test step fails to execute.|
|Error||Show only the log messages indicating that some error has occurred at a given step.|
|Warning||Show only the log messages indicating that a test step is failed but accepted as a warning.|
|Not Run||Show only the log messages indicating that a test step is skipped.|
Tabular view vs. Tree View
The Log Viewer can be viewed in different modes: tabular view and tree view. You can switch to tree view by selecting the Tree View toggle as illustrated below:
The Tree View display logs in a structural way that relates to how the test case/test suite organized. Additionally, users can now navigate to the respective step by selecting from the context menu, as shown below:
While the test is being executed, the Log Viewer is being updated with real-time log messages, where the most recent log messages is shown at the bottom. Therefore, the Log Viewer keeps scrolling down during the test execution. However, users may want to keep the Log Viewer standing still so that they can verify particular log message. To stop this scrolling behavior, you can select Scroll Lock.
Customize Console Log
Execution Progress Debugger
Katalon Studio execution log displays complete details of actions performed during the test run to help you debug better. The test log contains all relevant information about the test run. Full test step statements and desired capabilities information are also included. Log levels are ANSI color-coded for different kinds of levels: INFO, DEBUG, WARING, ERROR for an easier view of the execution log, as shown in the screenshot below.
In the Log Viewer, the Status Bar helps you quickly get the status of the recent tests run. When there are FAILED or ERROR tests from a current job, the status bar has the RED color to indicate such, and GREEN color for tests run with PASSED status. (For Windows only)
Extensive logs for Web Service testing
Sending and receiving Web Service can be a troublesome task due to many factors involved on both client and server sides. Since version 5.9, Katalon Studio has included the
HAR file in Web Service execution’s log. The
HAR file contains low-level data to help you identify the critical performance problems with Web services quickly.
Upon sending requests, a relative
.har file is recorded and made accessible from execution logs. The file is stored directly on the current executed machine.
.har files are stored in the requests' main folder under the generated report folders if you execute Web Service Suites.
.har file in services analyzer such as https://toolbox.googleapps.com/apps/har_analyzer/ will provide quality insights about the Web Service request and response. This will help the project team quickly identify key issues and efficiently allocate resources to address the issue. Some issues that can be identified include:
- Performance issues: slow page load, timeout when performing a specific task
- Page rendering issues: incorrect page format or missing information
The deepest level of logs called TRACE. Use the TRACE level when you need more logs details than DEBUG level, which is used by default. You can also lessen the logs' details by using the INFO level.
In case you want to change the log’s level of one or multiple packages, this setting is located and stored in Include > Config >
By uncommenting logging.level.com.kms=TRACE line, the differences are noticeable
Log executed test steps
Starting from Katalon Studio version 7.0, an option to disable Log executed test steps is available in Project Settings > Executions. By enabling or disabling this option, you can decide whether the logs include executed test steps.
- Katalon Studio execution logs are enhanced for a better debugging process and observation of execution progress.
- Logs level can be configured directly from the
.harfile is generated and stored in Web Service request logs. It can be used to analyze and troubleshoot performance or connection issues (if any).
- Logs can be set to include or exclude the executed test steps.