[
https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816969#comment-16816969
]
Stig Rohde Døssing commented on SUREFIRE-1546:
----------------------------------------------
[~marcphilipp]
The example you posted looks great, and is pretty much how I would want it to
work. Having the console flatten the tree and print it would be good.
For the solution you mentioned as being possible without the new reporting
format, I'd be happy to try adding the display name of the container to the
invocation display name in RunListenerAdapter. Would it make sense to assume we
want to prefix the container display name if the container TestIdentifier has a
MethodSource, and otherwise not? (so we don't end up prefixing with e.g. the
containing class)
> 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)
