[
https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816383#comment-16816383
]
Stig Rohde Døssing commented on SUREFIRE-1546:
----------------------------------------------
This change causes parameterized tests to lose the method name in the console
output.
For example, running a parameterized test called TestWindowCount declared as
{code}
@ParameterizedTest
@MethodSource(value = "generateCountWindows")
public void testWindowCount(int windowSize, int slideSize) throws Exception
{code}
gives this output
{quote}
[ERROR] org.apache.storm.st.tests.window.SlidingWindowTest.[7] 5, 10 Time
elapsed: 88.167 s <<< FAILURE!
{quote}
Note the missing method name. I don't think this is a good default behavior.
The discussion at
https://github.com/junit-team/junit5/issues/1496#issuecomment-404178095 seems
to imply that excluding the method name is intentional. I think it would be
nicer if the method name were included by default, but I'm not sure if the
issue belongs here (since Surefire could include the method name in the
output), or in JUnit (since the default displayName for parameterized tests
could be changed). What do you think?
> 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)
