Reg.: Reporting for nested test cases in the reports

Web Testing
2

Problem Analysis

You’re experiencing a common behavior in Katalon Studio: when test cases are called within other test cases (nested structure), only the parent test case appears in the test report, not the called test cases. This is by design—called test cases are executed as test steps within the parent test case, not as independent test case executions.

Solutions

Solution 1: Add All Test Cases Directly to the Test Suite (Recommended)

This is the most straightforward approach if you want each test case to appear as a separate entry in the test report.

Steps:

  1. Open your Test Suite
  2. Click Add to add test cases
  3. Add Test Case #1, Test Case #2, and Test Case #3 as separate test cases in the suite (instead of calling them from within each other)
  4. Execute the test suite
  5. All three test cases will now appear as separate entries in the test report with individual status, timing, and logs

Advantage: Each test case has its own execution status, detailed logs, and timing information in the report.

Solution 2: Keep Nested Structure but View Called Test Case Details

If you need to maintain the nested structure for code reusability, you can still see the details of called test cases in the test logs:

Steps:

  1. After test execution, open the Test Report
  2. Navigate to the Test Log section for the parent test case
  3. Expand the test steps to see detailed execution logs of the called test cases
  4. Each called test case will appear as a test step with its own execution details, including:
    • Step name (the called test case name)
    • Execution status (Passed/Failed/Error)
    • Duration
    • Detailed logs and screenshots

Advantage: Maintains code reusability while providing visibility into nested test case execution.

Solution 3: Combine Both Approaches

For comprehensive reporting:

  1. Add the parent test case to the test suite (Test Case #1)
  2. Also add the child test cases directly to the test suite (Test Case #2, #3)
  3. Keep the nested calls within Test Case #1 for reusability
  4. This gives you both the nested execution flow AND separate test case entries in the report

Key Considerations

Why Called Test Cases Don’t Appear as Separate Entries:

  • According to Katalon’s documentation on calling test cases, when you use callTestCase() or the “Call Test Case” step, the called test case is executed as a test step within the calling test case, not as an independent test case execution.
  • This is intentional design to support code reusability and modular test structure.

Test Report Behavior:

  • The test report summary shows only the top-level test cases that were directly added to the test suite
  • Called test cases are visible in the detailed test logs as individual steps
  • When viewing test reports, you can expand each test case to see all nested steps and their execution details

References

1 Like