Where to check the result of aborted test

[arvind.choudhary]

I schedule the regression test collection weekly on VM server with the help of Katalon agent, sometime I see 1-2 test suite get aborted in middle and close and execution engine picks up the next suite to execute and in this way it completes. Next day when I try to check the log file or the debug file, it shows that any particular suite got skipped but it didn’t have end-to-end detail about what went wrong during execution.
So below you can see in the starting the list is in the image

Now after sometime, I can see the message in the log that it is closing the 1st test suite and providing the result in the filepath under the tmp folder, but as that is temporary folder so I cannot find any file there to check what happened

Now after sometime I can see clearly it simply skipped the 1st test suite and started executing the next suite.

Now from where I check the result about what happened to the 1st suite.

And at the last of the test suite I can see the message as Exit code 1

Can someone help me in this problem? I need quick support

Regards,
Arvind Kumar C

[depapp]

hi @arvind.choudhary

AFAIK when a test suite or test run is aborted/skipped during execution, it won’t show a full detailed report like a normal completed run because katalon doesn’t generate a full suite report unless the execution finishes as expected.

but you can try this approach, for runs that are aborted early (especially from command-line/CI agents), katalon often writes temp logs in the system temp area (not just the normal Reports folder). for example:

…/Temp/Katalon/Test Suites/<SuiteName>/<timestamp>/execution0.log

and maybe you can try this one also

• enable console logging and TRACE level before running so temp logs have more detail.
• if running from CI (jenkins/gitlab), redirect console output to a file so you’ll capture early errors too.

[arvind.choudhary]

Thanks for the quick response
@depapp

[akshay_sartabe]

I faced similar issue around 5-6 months back, and the main reason for that was the tests in that suite were getting timed out. This time-out is there in the Advanced Settings section. By default it is 180 mins. Meaning if the tests in the suite are not completed in 180 mins then that suite gets cancelled.

Try setting it to max value i.e 999 mins.

At least this worked for me at that time.

[arvind.choudhary]

@akshay_sartabe , I have made changes in the setting and increased the time limit to 999, I hope my issue will also get resolved
Thanks buddy

[Monty_Bagati]

Based on the forum post and Katalon Studio documentation, here’s a comprehensive answer to Arvind Choudhary’s question about finding aborted test results:

---

Problem Analysis

You’re running regression test collections on a VM server with Katalon agent, and occasionally 1-2 test suites get aborted mid-execution. When you try to find the logs or debug files, you can’t locate the information about what happened to the aborted suite.

Where to Check Aborted Test Results

According to the Katalon Studio documentation on execution logs, here are the locations to check:

1. Log Viewer in Katalon Studio (Primary Location)

After test execution completes (even if aborted), check the Log Viewer tab:

• Location: Bottom panel of Katalon Studio after test execution
• What it shows:
  • Pass/Fail status of each test step
  • Error messages and exceptions
  • Browser, platform, and Selenium version info
  • Session ID and execution metadata
  • Detailed logs of what happened before the abort

How to view:

1. After test execution, click the Log Viewer tab
2. Switch between Tabular View and Tree View for different perspectives
3. Expand individual test steps to see detailed logs
4. Look for ERROR or EXCEPTION messages that caused the abort

2. Report Folder (File System)

The test reports are stored in your project’s Reports folder:

• Default path: <Your_Project>/Reports/
• Report structure: Each execution creates a timestamped folder (e.g., 20230608_112253/)
• Files to check:
  • execution.log - Main execution log file
  • JUnit_Report.xml - Test results in XML format
  • .har files (for Web Service tests) - Located in requests/main/ subfolder
  • .properties files - Execution metadata

How to access:

Right-click on the Report folder → "Open containing folder"

3. Console Output

• Location: Console tab in Katalon Studio
• What it shows: Real-time execution logs with color-coded levels (INFO, DEBUG, WARNING, ERROR)
• For aborted tests: Look for ERROR or EXCEPTION messages that indicate why the suite was aborted

4. Increase Log Detail Level (For Debugging)

If the default logs don’t show enough detail, enable TRACE level logging:

Steps:

1. Go to Include > Config > log.properties in your project

2. Uncomment this line:

   logging.level.com.kms=TRACE
   

3. Re-run the test suite

4. Check the Log Viewer again for more detailed logs

5. Enable “Log Executed Test Steps”

To capture more detailed step-by-step information:

1. Go to Project Settings > Executions
2. Enable “Log executed test steps”
3. Re-run the test suite
4. Check the Log Viewer for detailed step information

---

Common Reasons for Aborted Tests

Based on the forum discussion, aborted tests are typically caused by:

Cause	How to Identify	Where to Check
Memory/Resource Issues	Out of memory errors	Console log, execution.log
Driver Crash	WebDriver session terminated	Log Viewer - look for “sessionId” errors
Network Timeout	Connection lost to test server	Console log - timeout messages
VM Agent Failure	Katalon agent process crashed	VM system logs, Katalon agent logs
Test Suite Configuration	Incorrect test suite setup	Test Suite definition, execution order

---

Recommended Troubleshooting Steps

1. Check the Log Viewer first - It’s the fastest way to see what happened
2. Open the Reports folder - Review the execution.log file for detailed information
3. Enable TRACE logging - Re-run the test with higher log detail
4. Check VM resources - Monitor CPU, memory, and disk space during execution
5. Review Katalon agent logs - Check the agent’s own log files on the VM

---

References

• View and Customize Execution Log in Katalon Studio
• Katalon Academy: How To Work With Execution Logs and Test Reports

---

Key Takeaway: The Log Viewer in Katalon Studio is your primary source for understanding aborted tests. If that doesn’t provide enough detail, check the Reports folder on the file system and enable TRACE level logging for deeper insights.

[j61]

@akshay_sartabe

I faced similar issue around 5-6 months back, and the main reason for that was the tests in that suite were getting timed out. This time-out is there in the Advanced Settings section. By default it is 180 mins. Meaning if the tests in the suite are not completed in 180 mins then that suite gets cancelled.

Try setting it to max value i.e 999 mins.

At least this worked for me at that time.

Extending the timeout is the correct fix just make sure the agent machine does not go to sleep during the extended run

[sneha.sajeev]

1. Increase JVM memory for KRE

In Agent startup or KRE command:

-Xms1024m
-Xmx4096m

2. Force browser cleanup between suites

Add a Test Listener:

@AfterTestSuite
def closeAll() {
    WebUI.closeBrowser()
}

3. Disable video recording if enabled

Video recording causes crashes in long runs.

4. Use compatible browser + driver

Lock versions:

• Chrome

• ChromeDriver
  Do NOT rely on auto-update on VM.

5. Split large regression collections

Instead of:

• 1 huge Test Suite Collection

Use:

• Multiple smaller collections

• Scheduled sequentially

[akshay_sartabe]

I think what is marked as Solution is not the correct post here.