Hi Experts, need help
I have nested test-cases, i.e., test-case#1 calls test-case#2, and in turn test-case#2 calls test-case#3 & so on…
However, in the test-reports it shows only test-case#1
How to report all the nested test-cases ?
Kindly suggest, many thanks
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.
This is the most straightforward approach if you want each test case to appear as a separate entry in the test report.
Steps:
Advantage: Each test case has its own execution status, detailed logs, and timing information in the report.
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:
Advantage: Maintains code reusability while providing visibility into nested test case execution.
For comprehensive reporting:
Why Called Test Cases Don’t Appear as Separate Entries:
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.Test Report Behavior:
Let me add a bit of explanation.
I made a series of nested test cases. TC1 calls TC2 which calls TC3. A Test Suite calls the TC1.
When I ran the Test Suite, I got the following HTML report:
At a glance, only TC1 is included in the report. TC2 and TC3 seem not to be there.
However, the row of “TC1” contains the information of the “TC2” collapsed. The row of “TC2” contains the information of the “TC3”. You can extend the container rows by clicking as follows.
I think that this design of HTML report is good enough.
You don’t like this report design, do you? If so, please explain why and how you want it to be like.
Katalon’s built-in callTestCase(…) treats nested calls as part of the calling test case. That means the Test Execution Report (and TestOps test-case list) shows only the top-level test-case run. To get separate entries for the nested test-cases you must run them as independent test items (Test Suite / Test Suite Collection) or explicitly create separate result entries yourself.
Recommended approaches (pick one depending on your needs)
Create a Test Suite that includes test-case#1, test-case#2, test-case#3 (order them so dependencies are preserved). When you run the Test Suite each test case produces its own report entry and status.
If you need grouped runs, use a Test Suite Collection to orchestrate multiple Test Suites.
When to use: you want standard Katalon reporting (html, junit, TestOps) with separate pass/fail per test case.
callTestCase will still show a single test-case entry, but you can make the report more informative by adding explicit logging at start/end of each nested test-case. Those logs appear in the HTML report and test logs, but not as separate test-case rows.
Example (inside each test case):
import com.kms.katalon.core.util.KeywordUtil
KeywordUtil.logInfo(‘START: TC-002 - Verify Login’)
KeywordUtil.logInfo(‘END: TC-002 - Verify Login - PASSED’)
If you use Katalon TestOps and need hierarchical/child test items, you can use the TestOps REST API (or any custom integration) to push custom test result items from inside a nested test-case. This requires implementing calls to TestOps API or your reporting backend in a custom keyword.
Use this when you need to keep callTestCase structure but still require separate test items in TestOps or a custom dashboard.
Concrete options and samples
A) Quick fix: change how you run tests
B) Logging improvement (simple custom keyword)
// Keyword class (Groovy) package custom.logging
import com.kms.katalon.core.annotation.Keyword import com.kms.katalon.core.util.KeywordUtil
class TCLogger { @Keyword def startCase(String id) { KeywordUtil.logInfo(“— START ${id} —”) }
@Keyword
def endCase(String id, boolean passed=true) {
if (passed) KeywordUtil.logInfo("--- END ${id} : PASSED ---")
else KeywordUtil.markFailed("--- END ${id} : FAILED ---")
}
}
Note: These appear in the test case log and HTML report, but they do not create separate test-case rows in the Katalon generated report.
C) Advanced: push separate results to TestOps
Which approach to choose?
If you want simple, standard reporting per test-case: restructure runs using Test Suites (option 1). This is the simplest and most maintainable.
If you must keep nested callTestCase architecture but need better visibility: add structured logs (option 3) or push results to TestOps with a custom integration (option 4).
Thanks everyone for your valueable replies
Passed 1
Here, in the test ops report, I want say 10 or 15, as the case maybe, instead of 1
In that case, you need to stop nesting test cases using the callTestCase keyword. You need to bind your 10 or 15 test cases in your test suite.
But I wonder why you want to see 10 or 15 instead of 1 here. Do you really need it? Why?
In my case, I would be interested only in the number of Failed test cases in a Test Suite; if it is 0 or >0 (more than zero).
If the number of Failed test cases is 0, I would be happy and go home.
If the number of Failed test cases is >0, regardless how many, I would continue working to fix all the failures until I see 0. The exact number of Passed/Failed test cases doesn’t really matter to me.
ok thanks Kazurayam
I will check
Respectfully, AI has come up with a misleading answer here:
”Solution 1: Add All Test Cases Directly to the Test Suite (Recommended)”
Any test case that cannot run as a standalone test cannot be added to the test suite without further work (eg any web test that lacks an ‘Open Browser’ step for example). The answer above is correct if the user wants to see a clear pass/fail for that part of the process but I thought it was worth pointing out that they might need extra work to do so, since there are always some tradeoffs in every approach!
Thanks everyone for your valueable answers
Have you found the answer for your issue? Feel free to share the workaround and mark the solution for reference to others. Thank you
