[
https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816570#comment-16816570
]
Stig Rohde Døssing commented on SUREFIRE-1546:
----------------------------------------------
[~marcphilipp] That would be nice. So for parameterized tests it could look like
{code}
com.somepackage.TestClass > bar(int) > [1] 54
{code}
if you were using the default DisplayName
(https://junit.org/junit5/docs/current/api/org/junit/jupiter/params/ParameterizedTest.html#DEFAULT_DISPLAY_NAME).
What if you set a custom DisplayName? Would it look like
{code}
com.somepackage.TestClass > bar(int) > myDisplayName
{code}
?
> 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)
