Errored test case count is not count in test suite collection

Miscellaneous
,
1

Dear community,

I have a issue with test suite collection report.

I don’t see test case errored count on report as image attached

Thanks all !

new 1.html (408.3 KB)

2

:hammer_and_wrench: Option 1: Customize the Report Template (Recommended)

Katalon uses FreeMarker templates for reports. Here’s how to add an “Errored” counter:

  1. Locate the report template:
    Go to:
    [Katalon_Install_Dir]/configuration/report-viewer/templates/default

  2. Edit summary.ftl:
    Open the file and find the section rendering test counts (look for failedCount). Add this code:

    text

    <#assign erroredCount = testCases?filter(tc -> tc.status == "ERROR")?size> <div class="col-md-2 col-sm-4 col-xs-6"> <div class="status status-error">${erroredCount}</div> <div class="status-text">Errored</div> </div>

  3. Update style.css:
    Add this to distinguish errors visually:

    css

    .status-error { background-color: #ff6b6b; } /* Red color */

  4. Regenerate your report → Errors will now appear as a separate counter.

:bar_chart: Option 2: Use Built-in “Test Failure Analysis” (Katalon 10.0+)

If you don’t want to edit templates:

  1. After test execution, go to “Test Failure Analysis” tab in Katalon.

  2. Filter by “Status: Error” → This shows only errored test cases.

  3. Export this list to Excel/PDF for stakeholders.

:robot: Option 3: Automate with Groovy (Pre-Execution Hook)

Add this to your @Startup script to log errors separately:

groovy

importcom.kms.katalon.core.context.TestCaseContext TestFailureCollector.addFailureCollector({ TestCaseContext context -> if(context.getTestCaseStatus() == TestCaseStatus.ERROR) { println "[ERRORED] ${context.getTestCaseId()}" // Write to custom log file newFile("errored_cases.log") << "${context.getTestCaseId()}\n" } })

→ Parses errors during execution and saves them to errored_cases.log.

:warning: Critical Notes:

  1. “Errored” vs “Failed”:

    • Error = Unhandled exception (e.g., missing object, network timeout).

    • Failed = Assertion failure (e.g., element not visible when expected).
      → If your tests never throw unhandled exceptions, you won’t have “Errored” cases.

  2. Katalon Version Matters:

    • Katalon 10.0+ (current latest: 10.5.1) has better error tracking.

    • Older versions (<9.0) cannot separate errors without template edits.

  3. Your Attached Report (new 1.html):
    This is the default Katalon report — it always combines errors into “Failed.” Customization is required to fix this.

:rocket: Pro Tip: Use Katalon TestOps for Advanced Reporting

If you have Katalon TestOps (enterprise):

  1. Sync reports to TestOps → Go to “Analysis” → “Failure Types”.

  2. It automatically categorizes “Errors” vs “Failures” with detailed root-cause analysis.

3

Welcome, @tungtm1! :tada: Looking forward to hearing more about your progress, feel free to share your updates here.

4

Hi @tungtm1,

Welcome to our community. Thank you for sharing your issue. Can you please try to create another simple test suite and run if it reports correctly or not? Otherwise, which KS version are you using? Thank you