Katalon Studio emits runtime logs into
:~/katalon-workspace/ReportWriterDriver (master #)
$ tree Reports -s
├── [ 96] 20211117_145442
│ └── [ 96] TS1
│ └── [ 320] 20211117_145442
│ ├── [ 197916] 20211117_145442.html
│ ├── [ 1803] JUnit_Report.xml
│ ├── [ 2663] execution.properties
│ ├── [ 36] execution.uuid
│ ├── [ 127247] execution0.log <====== THIS!
│ ├── [ 144] testCaseBinding
│ ├── [ 0] tsc_id.txt
│ └── [ 128] videos
│ ├── [ 861216] screen_recording_1_0.avi
│ └── [ 10079] screen_recording_1_0.srt
└── [ 96] Self-healing
└── [ 31] broken-test-objects.json
5 directories, 10 files
The content of the
execution0.log file is something like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE log SYSTEM "logger.dtd">
<message>Start Test Suite : Test Suites/test/All</message>
<property name="id">Test Suites/test/All</property>
execution0.log file is generated by the Java Standard Logging framework:
The content of
execution0.log file is exactly the same as what we see in the Log Viewer in the Katalon Studio GUI. This means, the
execution0.log file contains the on-going results as a test suite is running.
Katalon Studio transforms the
execution0.log file to what we call “Basic Report as HTML” and “JUnitReport as XML”.
Therefore, if you want a means to access on-going results as a test/suite is running, then you want 2 things:
You want to trigger Katalon Studio to do
execution0.log --> HTML report transformation intentionally even when a Test Suite has crashed for some reason.
When you forcefully stoped Katalon Studio because the Test Suite got frozen, then the
execution0.log file might become a mal-formed XML document. For example,
- the file may miss the closing
</log> tag at the end of the file
<record> tag may be broken at the end of the file.
execution0.log file is generated when a Test Suite has finished (regardless with failure or not). I am not sure how the log file will be generated when the OS process was stopped irregularly.
Do you want Katalon studio to be capable of transforming a mal-formed
execution0.log to a well-formed Basic HTML report? I do not think it is possible to implement.
A super-skillful Java programmer may be able to write a purifier tool that accept a mal-formed
execution0.log file to make it a well-formed XML. Then the magic may become possible. — sorry, I am not capable.