maven-issues mailing list archives

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

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

Tibor Digana commented on SUREFIRE-1546:
----------------------------------------

No. Not yet, because this may break the users after a new config possibilities.
One version with this behavior and another experience in later version.
If you really like this preliminary result, you can use the SNAPSHOT version which is deployed
at {{repository.apache.org}} Nexus.
Currently {{SUREFIRE-1585}} (JUnit5 feature) is going be finished with more unit tests and
then {{SUREFIRE-1222}}.

> 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