🐞: Allure Report Displays Multiple Scenarios for Karate callonce & call Invocation

umitozdemirf

What happened?

When using callonce in Karate, the Allure report displays the called scenario as a separate test case. This behavior increases the number of scenarios shown in the report, which can be misleading when trying to analyze test results.

Steps to Reproduce:
Write a Karate test that uses callonce to call another feature file.
Run the test and generate an Allure report.
Observe that the scenario invoked by callonce appears as a separate test case.
Expected Behavior:
The callonce-invoked scenario should ideally:

Be nested under the main test case, or
Not appear as a separate test case in the report.
Actual Behavior:
The callonce-invoked scenario is listed as a separate test case, which creates confusion about the actual number of executed tests.

Questions:
Is this the expected behavior for Karate with Allure integration?
Are there recommended configurations or workarounds to handle this more effectively?
Contribution:
If this is a confirmed issue or an enhancement opportunity, I’d like to contribute to finding and implementing a solution.

Thank you.

What Allure Integration are you using?

allure-karate

What version of Allure Integration you are using?

2.22.0

What version of Allure Report you are using?

2.22.0

Code of Conduct

I agree to follow this project's Code of Conduct