如何在Cucumber报告中显示Karate调用的Feature/Scenario标题？

Absolutely feasible! I’ve tackled this exact problem with large Cucumber test suites before, and there are a couple of solid approaches to make your reports way more readable. Let’s break down the best options:

1. Wrap call Statements in Descriptive Steps (Simplest Approach) #

Instead of dropping raw call classpath:... lines directly into your main scenario, encapsulate them into human-readable steps. This is the easiest way to fix your report readability without custom code.

Example Gherkin: #

# Main Scenario Feature
Feature: End-to-End User Journey
  Scenario: Complete User Onboarding & Purchase
    Given I run the "User Registration Workflow" scenario from "auth/registration.feature"
    And I execute the "Product Checkout Flow" scenario from "shopping/checkout.feature"
    Then verify the order is marked as completed

Step Definition (Java Example): #

@Given("I run the {string} scenario from {string}")
public void runScenario(String scenarioTitle, String featurePath) {
    // Use Cucumber's API to call the target feature/scenario
    RuntimeOptions runtimeOptions = new RuntimeOptionsBuilder()
        .addFeature(featurePath)
        .addScenario(scenarioTitle)
        .build();
    new Runtime(runtimeOptions).run();
}

Now your Cucumber report will show the descriptive step text instead of the raw call command, making it instantly clear which workflows were executed.

2. Custom Cucumber Formatter (For Automated Title Extraction) #

If you don’t want to rewrite all your call statements, you can build a custom report formatter that automatically parses the called feature file and replaces the call classpath:... text with the actual scenario title.

Example Custom Formatter (Java): #

import io.cucumber.core.api.Scenario;
import io.cucumber.core.feature.FeatureParser;
import io.cucumber.core.plugin.PrettyFormatter;
import io.cucumber.core.gherkin.Step;

import java.io.File;

public class CallStepFormatter extends PrettyFormatter {

    @Override
    public void stepStarted(Step step) {
        String stepText = step.getText();
        // Detect if this is a call step
        if (stepText.startsWith("call classpath:")) {
            String featurePath = stepText.replace("call classpath:", "").trim();
            // Extract the scenario title from the feature file
            String scenarioTitle = getScenarioTitleFromFeature(featurePath);
            // Create a modified step with the title instead of the path
            Step customStep = new Step(step.getKeyword(), scenarioTitle, step.getLocation(), step.getParameters());
            super.stepStarted(customStep);
        } else {
            super.stepStarted(step);
        }
    }

    private String getScenarioTitleFromFeature(String featurePath) {
        // Adjust the path to point to your resources directory
        File featureFile = new File("src/test/resources/" + featurePath);
        io.cucumber.core.gherkin.Feature feature = FeatureParser.parse(featureFile);
        // Assumes the feature has one scenario - adjust if you have multiple
        return feature.getScenarios().get(0).getName();
    }
}

How to Use: #

When running your tests, specify the custom formatter as a plugin:

mvn test -Dcucumber.plugin=com.yourpackage.CallStepFormatter,html:target/cucumber-report.html

This will automatically replace all call classpath:... entries in your report with the corresponding scenario title.

Key Notes: #

• Cucumber Version: Make sure you’re using Cucumber 6.x or newer—some of the API used in the custom formatter changed in earlier versions.
• Multiple Scenarios: If your feature files have multiple scenarios, adjust the getScenarioTitleFromFeature method to match the specific scenario being called (you might need to pass the scenario name in the call command or parse tags).
• Maintenance: The wrapped step approach is more maintainable long-term, as it makes your Gherkin more readable for non-technical stakeholders too.

内容的提问来源于stack exchange，提问作者backfloep