JUnit 5 Parameterized Tests and CI/CD Report Integration

Managing Test Output Volume

When utilizing @ParameterizedTest in JUnit 5 (Jupiter), a single test method may execute hundreds of iterations. While the name attribute allows for descriptive identifiers, the resulting volume of successful iterations can create significant noise within CI/CD logs and XML reporting artifacts.

The goal is to maintain a high level of granularity for failures while minimizing the footprint of successful iterations in the final test report. There is uncertainty regarding the most efficient way to balance @DisplayNameGeneration with standard JUnit XML output to ensure that only actionable failures are highlighted without losing the traceability of the input parameters.

Does JUnit 5 provide a native mechanism to suppress successful parameterized iterations from the XML report while retaining them for failed ones? If not, what is the recommended integration pattern to filter these results at the reporting boundary?