Unable to change Junit naming strategy

[grappler]

👓 What did you see?

The test name is "The scenario outline - #1.1: The example scenario outline" even with the following config.

@ConfigurationParameter(
        key = JUNIT_PLATFORM_NAMING_STRATEGY_PROPERTY_NAME,
        value = "short"
)
@ConfigurationParameter(
        key = JUNIT_PLATFORM_SHORT_NAMING_STRATEGY_EXAMPLE_NAME_PROPERTY_NAME,
        value = "pickle"
)

Junit Report

<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="Cucumber" time="0.567" tests="1" skipped="0" failures="0" errors="0" timestamp="2025-10-03T14:19:28.818825900Z">
<testcase classname="An example that has evolved further" name="The &lt;scenario name&gt; scenario outline - #1.1: The example scenario outline" time="0.005">
<system-out><![CDATA[
Given an example scenario outline...........................................passed
When all step definitions are implemented...................................passed
Then the scenario passes....................................................passed
]]></system-out>
</testcase>
</testsuite>

✅ What did you expect to see?

The test name is "The example scenario outline"

<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="Cucumber" time="0.567" tests="1" skipped="0" failures="0" errors="0" timestamp="2025-10-03T14:19:28.818825900Z">
<testcase classname="An example that has evolved further" name="The example scenario outline" time="0.005">
<system-out><![CDATA[
Given an example scenario outline...........................................passed
When all step definitions are implemented...................................passed
Then the scenario passes....................................................passed
]]></system-out>
</testcase>
</testsuite>

📦 Which tool/library version are you using?

cucumber-jvm v7.30
junit 6.0.0

🔬 How could we reproduce it?

Here is an example.

package hellocucumber;

import static io.cucumber.junit.platform.engine.Constants.*;

import org.junit.platform.suite.api.ConfigurationParameter;
import org.junit.platform.suite.api.IncludeEngines;
import org.junit.platform.suite.api.SelectPackages;
import org.junit.platform.suite.api.Suite;

@Suite
@IncludeEngines("cucumber")
@SelectPackages("hellocucumber")
@ConfigurationParameter(
  key = PLUGIN_PROPERTY_NAME,
  value = "pretty," +
    "junit:target/cucumber-reports/cucumber.xml,"
)
@ConfigurationParameter(key = GLUE_PROPERTY_NAME, value = "hellocucumber")
@ConfigurationParameter(
        key = JUNIT_PLATFORM_NAMING_STRATEGY_PROPERTY_NAME,
        value = "short"
)
@ConfigurationParameter(
        key = JUNIT_PLATFORM_SHORT_NAMING_STRATEGY_EXAMPLE_NAME_PROPERTY_NAME,
        value = "pickle"
)
class RunCucumberTest {}

Feature: An example that has evolved further

  Scenario Outline: The <scenario name> scenario outline
    Given an <scenario name> scenario outline
    When all step definitions are implemented
    Then the scenario passes

    Examples:
      | scenario name |
      | example        |

package hellocucumber;

import io.cucumber.java.en.Given;
import io.cucumber.java.en.Then;
import io.cucumber.java.en.When;

public class StepDefinitions {

  @Given("^an (.+) scenario outline$")
  public void anExampleScenarioOutline(String scenarioName) {
      if (scenarioName.equals("example")) {
        // Nothing to do: demo
      }
  }

  @When("all step definitions are implemented")
  public void allStepDefinitionsAreImplemented() {
    // Nothing to do: demo
  }

  @Then("the scenario passes")
  public void theScenarioPasses() {
    // Nothing to do: demo
  }
}

📚 Any additional context?

#2860
#3004

[mpkorstanje]

The cucumber.junit-platform.* properties control how Cucumber maps a feature file to JUnit Platform test descriptors. This is useful when running Cucumber through JUnit 5, and then running JUnit 5 through Maven, Gradle or the JUnit Console Launcher (see diagram). The junit plugin listens directly to Cucumber and is unware of the JUnit Platform.

At present plugins for Cucumber can't be configured other than their output file (#1834). So you have two options:

a) Use the cucumber.junit-platform.* properties and report generated by Gradle or the JUnit Console Launcher.
b) Create your own custom plugin and configure it:

package io.cucumber.skeleton;

import io.cucumber.junitxmlformatter.MessagesToJunitXmlWriter;
import io.cucumber.messages.types.Envelope;
import io.cucumber.plugin.ConcurrentEventListener;
import io.cucumber.plugin.event.EventPublisher;
import io.cucumber.query.NamingStrategy;

import java.io.IOException;
import java.io.OutputStream;

public final class MyJUnitFormatter implements ConcurrentEventListener {
    private final MessagesToJunitXmlWriter writer;

    public MyJUnitFormatter(OutputStream out) {
        this.writer = new MessagesToJunitXmlWriter(NamingStrategy.ExampleName.PICKLE, out);
    }

    public void setEventPublisher(EventPublisher publisher) {
        publisher.registerHandlerFor(Envelope.class, this::write);
    }

    private void write(Envelope event) {
        try {
            this.writer.write(event);
        } catch (IOException e) {
            throw new IllegalStateException(e);
        }

        if (event.getTestRunFinished().isPresent()) {
            try {
                this.writer.close();
            } catch (IOException e) {
                throw new IllegalStateException(e);
            }
        }

    }
}

Then enable it by:

@ConfigurationParameter(key = PLUGIN_PROPERTY_NAME, value = "io.cucumber.skeleton.MyJUnitFormatter:target/cucumber.xml")

Note that the MessagesToJunitXmlWriter will currently always use the long strategy, but should be relatively simple to address with a pull request.

[grappler]

Thank you very much for such a detailed response.

Initially, I had copied and modified some classes from junitxmlformatter, but now I wanted to use a cleaner solution. I tried the custom Formater, but there was not an option to pass the short strategy.

I have created a PR: cucumber/junit-xml-formatter#105