Context

Problem

• Steps like call and callonce were being treated as separate test scenarios.
• This was inflating the test count in Allure and making the reports harder to read.

Solution

1. Locate the Issue:

   • Found that the issue was in the beforeStep and afterStep methods in the AllureKarate class.

2. Update beforeStep:

   • Added a check to skip steps that start with call or callonce:

     @Override
     public boolean beforeStep(final Step step, final ScenarioRuntime sr) {
         final String parentUuid = (String) sr.magicVariables.get(ALLURE_UUID);
         if (Objects.isNull(parentUuid)) {
             return true;
         }
     
         // Skip 'call' and 'callonce' steps
         if (step.getText().startsWith("call") || step.getText().startsWith("callonce")) {
             LOGGER.info("Skipping Allure for call/callonce: " + step.getText());
             return true;
         }
     
         final String uuid = parentUuid + "-" + step.getIndex();
         final io.qameta.allure.model.StepResult stepResult = new io.qameta.allure.model.StepResult()
                 .setName(step.getText());
         lifecycle.startStep(parentUuid, uuid, stepResult);
     
         return true;
     }

3. Update afterStep:

   • Also skipped these steps in afterStep to avoid processing them as separate tests:

     @Override
     public void afterStep(final StepResult result, final ScenarioRuntime sr) {
         final String parentUuid = (String) sr.magicVariables.get(ALLURE_UUID);
         if (Objects.isNull(parentUuid)) {
             return;
         }
     
         final Step step = result.getStep();
     
         // Skip 'call' and 'callonce' steps
         if (step.getText().startsWith("call") || step.getText().startsWith("callonce")) {
             LOGGER.info("Skipping Allure for call/callonce: " + step.getText());
             return;
         }
     
         final String uuid = parentUuid + "-" + step.getIndex();
         final Result stepResult = result.getResult();
     
         final Status status = !stepResult.isFailed()
                 ? Status.PASSED
                 : Optional.of(stepResult)
                         .map(Result::getError)
                         .flatMap(ResultsUtils::getStatus)
                         .orElse(null);
     
         final StatusDetails statusDetails = Optional.of(stepResult)
                 .map(Result::getError)
                 .flatMap(ResultsUtils::getStatusDetails)
                 .orElse(null);
     
         lifecycle.updateStep(uuid, s -> {
             s.setStatus(status);
             s.setStatusDetails(statusDetails);
         });
         lifecycle.stopStep(uuid);
     }

4. Test the Fix:

   • After these changes, I tested the setup, and the call and callonce steps now show up as part of the parent scenario, not as separate tests.

Result

• Test counts in Allure are accurate now.
• Reports look much cleaner and more understandable.

Checklist

• Sign Allure CLA
• Provide unit tests