[
https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758735#comment-16758735
]
Tibor Digana commented on SUREFIRE-1546:
----------------------------------------
> I strongly suggest to not alter the XML format used by Ant/Surefire in an
> incompatible manner.
Dan is not aiming for a new format. As I have understood him, he wants to keep
the current XSD but only alter values (real or display).
I guess these users want to use User Scenario of BDD instead of real class name
like it is in Spock and every class is testing another scenario.
Personally I would prefer having new attributes and Jenkins plugins upgrades
but users do not require that right now however it can be added as late as
possible.
> JUnit 5 runner does not honor JUnit 5 display names
> ---------------------------------------------------
>
> Key: SUREFIRE-1546
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1546
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
> Affects Versions: 2.22.0
> Reporter: Romain Manni-Bucau
> Assignee: Tibor Digana
> Priority: Major
> Labels: junit5
> Fix For: 3.0.0-M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> JUnit 5 runner should respect the test @DisplayName instead of displaying the
> classname if any is defined. Seems last release doesn't support that feature
> of JUnit 5 making the console output and reports not the expected ones.
>
> Origin: https://github.com/junit-team/junit5/issues/990
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
