Legacy XML reports generated for `@ParameterizedClass` tests do not contain parameters

[amilbourne]

This issue stems from #5296 which was closed because the report in question was being generated by Gradle, but the same issue exists in JUnit 6.0.3.

If you have a test using @ParameterizedClass and get it to generate legacy reports, the parameters do not appear in the report and you just get lots of duplicate entries for each method. This makes it hard to tell which parameters failed and hard for other tools to process the report.

Steps to reproduce

I used the junit-platform-console-standalone-6.0.3.jar to run the test from the command-line

The test was:

import org.junit.jupiter.api.Test;
import org.junit.jupiter.params.ParameterizedClass;
import org.junit.jupiter.params.provider.ValueSource;

import java.util.Locale;

import static org.junit.jupiter.api.Assertions.*;

@ParameterizedClass(name="candidate={0}")
@ValueSource(strings = { "first", "second", "third" })
class ClassParamTest {

  private String candidate;

  public ClassParamTest(String candidate) {
    this.candidate = candidate;
  }

  @Test
  void notEmpty() {
    assertFalse(candidate.isEmpty());
  }

  @Test
  void isLowercase() {
    assertEquals(candidate.toLowerCase(Locale.ROOT), candidate);
  }
}

The build script was:

#!/bin/bash
cd ~/code/junit-test
JAR=junit-platform-console-standalone-6.0.3.jar
if [ ! -f "$JAR" ]; then
  curl -fL -o "$JAR" "https://repo1.maven.org/maven2/org/junit/platform/junit-platform-console-standalone/6.0.3/$JAR"
fi
mkdir -p out/test-classes reports
javac -cp "$JAR" -d out/test-classes test/ClassParamTest.java
java -cp "$JAR:out/test-classes" -jar "$JAR" execute -cp out/test-classes --reports-dir=reports --config=junit.platform.reporting.output.dir=reports --config=junit.platform.reporting.legacy.xml.enabled=true --scan-class-path

and the report generated was:

<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="JUnit Jupiter" tests="6" skipped="0" failures="0" errors="0" time="0.061" hostname="co1devps22.yb.lmax" timestamp="2026-02-26T17:39:08">
<properties>
<property name="file.encoding" value="UTF-8"/>
</properties>
<testcase name="isLowercase()" classname="ClassParamTest" time="0">
<system-out><![CDATA[
unique-id: [engine:junit-jupiter]/[class-template:ClassParamTest]/[class-template-invocation:#2]/[method:isLowercase()]
display-name: isLowercase()
]]></system-out>
</testcase>
<testcase name="isLowercase()" classname="ClassParamTest" time="0">
<system-out><![CDATA[
unique-id: [engine:junit-jupiter]/[class-template:ClassParamTest]/[class-template-invocation:#3]/[method:isLowercase()]
display-name: isLowercase()
]]></system-out>
</testcase>
<testcase name="notEmpty()" classname="ClassParamTest" time="0">
<system-out><![CDATA[
unique-id: [engine:junit-jupiter]/[class-template:ClassParamTest]/[class-template-invocation:#3]/[method:notEmpty()]
display-name: notEmpty()
]]></system-out>
</testcase>
<testcase name="notEmpty()" classname="ClassParamTest" time="0">
<system-out><![CDATA[
unique-id: [engine:junit-jupiter]/[class-template:ClassParamTest]/[class-template-invocation:#2]/[method:notEmpty()]
display-name: notEmpty()
]]></system-out>
</testcase>
<testcase name="notEmpty()" classname="ClassParamTest" time="0">
<system-out><![CDATA[
unique-id: [engine:junit-jupiter]/[class-template:ClassParamTest]/[class-template-invocation:#1]/[method:notEmpty()]
display-name: notEmpty()
]]></system-out>
</testcase>
<testcase name="isLowercase()" classname="ClassParamTest" time="0.013">
<system-out><![CDATA[
unique-id: [engine:junit-jupiter]/[class-template:ClassParamTest]/[class-template-invocation:#1]/[method:isLowercase()]
display-name: isLowercase()
]]></system-out>
</testcase>
<system-out><![CDATA[
unique-id: [engine:junit-jupiter]
display-name: JUnit Jupiter
]]></system-out>
</testsuite>

Note that I removed most of the properties as they are not really relevant

I would expect the test names to be something like:

<testcase name="isLowerCase[first]" classname="ClassParamTest" time="0.019"/>

Context

• Uses Jupiter 6.0.3

[amilbourne]

I wasn't sure whether to open this as a feature request or a bug, so apologies if it is more of a feature request.

[marcphilipp]

@amilbourne Thanks for the report!

I've checked what Gradle and Maven produce for @RunWith(Parameterized.class) in JUnit 4. Both append an index to each test case and look roughly like this:

<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="com.example.project.JUnit4Test" tests="4" skipped="0" failures="0" errors="0" timestamp="2026-03-02T14:03:47.198Z" time="0.013">
  <properties/>
  <testcase name="isLowercase[0]" classname="com.example.project.JUnit4Test" time="0.003"/>
  <testcase name="notEmpty[0]" classname="com.example.project.JUnit4Test" time="0.0"/>
  <testcase name="isLowercase[1]" classname="com.example.project.JUnit4Test" time="0.0"/>
  <testcase name="notEmpty[1]" classname="com.example.project.JUnit4Test" time="0.001"/>
</testsuite>

We do something similar for @ParameterizedTest:

junit-framework/junit-jupiter-engine/src/main/java/org/junit/jupiter/engine/descriptor/TestTemplateInvocationTestDescriptor.java

Lines 74 to 77 in a6e2a8b

	@Override
	public String getLegacyReportingName() {
	return super.getLegacyReportingName() + "[" + index + "]";
	}

I think we should also "inherit" indexes to children. When nesting a @ParameterizedTest or @ParameterizedClass within a @ParameterizedClass, that will mean multiple indexes, though.

[sbrannen]

Thanks for looking into the JUnit 4 parameterized test class use cases, @marcphilipp. 👍

I think we should also "inherit" indexes to children. When nesting a @ParameterizedTest or @ParameterizedClass within a @ParameterizedClass, that will mean multiple indexes, though.

I agree. That will result in some form of multiple indexes, but I don't see how that could be avoided with the legacy XML reporting format.

[amilbourne]

Thanks for responding quickly.
Using parameter indexes would certainly work.

However, ParameterizedTest and ParameterizedClass both allow the user to set a displayName, and it would be even nicer if this was used in the report (where specified). I guess there may be some minor issues with escaping or removing special characters (e.g. quotes), but this would make the report much more readable. I work with classed that have 4 or 5 parameters and a test result of the form name="isLowercase[0,1,0,3]" isn't super easy to read.

Actually, perhaps I misunderstood, when you talk about indexes, perhaps you mean something like a counter where each parameter combination is given an index rather than each parameter having its own individual index. So parameters a = [1,2] and b = [8,9] would result in indexes [0], [1], [2], & [3] rather than [0,0], [0,1], [1,0], & [1,1]. This would also work as long as the mapping between parameter set and index was constant. If it varied it would be very hard for subsequent tooling to identify which parameters had failed or whether a test was intermittent for a particular parameter set.

I have not looked at what JUnit 4 does in this respect and I understand that there is value in consistency.

[marcphilipp]

However, ParameterizedTest and ParameterizedClass both allow the user to set a displayName, and it would be even nicer if this was used in the report (where specified).

Except in the comment, the legacy XML format does not output display names. I think we could add the parent display names there as well.

Have you considered switching to the Open Test Reporting format which supports display names and hierarchical structures properly?

Actually, perhaps I misunderstood, when you talk about indexes, perhaps you mean something like a counter where each parameter combination is given an index rather than each parameter having its own individual index.

The index of each invocation of the parameterized class would be used, regardless of how many parameters it has.