You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@apache.org> on 2019/02/01 15:00:00 UTC
[jira] [Comment Edited] (SUREFIRE-1546) JUnit 5 runner does not
honor JUnit 5 display names
[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758382#comment-16758382 ]
Dan Tran edited comment on SUREFIRE-1546 at 2/1/19 2:59 PM:
------------------------------------------------------------
For reporting purpose. We parse TEST-*.xml under target/surefire-report to render the report at Micro Focus quality center.
So having displayName to replace the actual testcase's name and classname are so crucial for us.
{code:java}
<testcase name="test case using displayName" classname="class name using displayName" time="0"/>
{code}
We are also using https://github.com/BogdanLivadariu/bootstraped-multi-test-results-report to post report to jenkins as well
please please keep the implementation, or provide an option to activate it
was (Author: dantran):
For reporting purpose. We parse TEST-*.xml under target/surefire-report to render the report at Micro Focus quality center.
So having displayName to replace the actual testcase's name and classname are so crucial for us.
{code:java}
<testcase name="test case using displayName" classname="class name using displayName" time="0"/>
{code}
It works
> 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)