[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817083#comment-16817083 ]
Tibor Digana commented on SUREFIRE-1546: ---------------------------------------- [~Srdo] [~marcphilipp] I would understand method display name as runtime string, this way, and this may distinguish from JUnit4 style of parameterized annotation: {code:java} @ParameterizedTest @DisplayName(container = "a parameterized test (bar(int))", value = "bar({0})") void bar(@ValueSource(intValue = {15, 54}) int x) { ... } {code} then it would become: {noformat} JUnit Jupiter └── Some tests (com.acme.SomeTests) └── a parameterized test (bar(int)) ├── bar(0) └── bar(1) {noformat} WDYT? > 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)