maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Tran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names
Date Fri, 01 Feb 2019 16:31:00 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758478#comment-16758478
] 

Dan Tran commented on SUREFIRE-1546:
------------------------------------

correction, we are not parsing the content of display name but for reporting purpose only.
And also agree, we must not break the compatibility

so using an additional surefire config should be perfect for us

> 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)

Mime
View raw message