[SUREFIRE-1737] Disabling the JUnit5Xml30StatelessReporter has no effect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M4
• Fix Version/s: 3.5.1
• Assignee: Slawomir Jaranowski
• Reporter: Dietrich Schulten
• Created: 12/Dec/19 14:56
• Updated: 22/Sep/24 17:48
• Resolved: 22/Sep/24 17:48

Description

I have the following configuration for JUnit 5 display names:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <version>3.0.0-M4</version>
    <configuration>
        <statelessTestsetReporter implementation="org.apache.maven.plugin.surefire.extensions.junit5.JUnit5Xml30StatelessReporter">
            <disable>true</disable>
            <usePhrasedFileName>true</usePhrasedFileName>
            <usePhrasedTestSuiteClassName>true</usePhrasedTestSuiteClassName>
            <usePhrasedTestCaseClassName>true</usePhrasedTestCaseClassName>
            <usePhrasedTestCaseMethodName>true</usePhrasedTestCaseMethodName>
        </statelessTestsetReporter>
    </configuration>
</plugin>

Based on the disable flag, the JUnit5Xml30StatelessReporter should be disabled, but it evaluates display names according to the usePhrasedXXX flags.

Issue Links

• links to: GitHub Pull Request #780