[jira] [Commented] (SUREFIRE-2065) Test Reports Inconsistencies with Parameterized and junit4

["Christian Marquez Grabia (Jira)" <ji...@apache.org>]

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

Christian Marquez Grabia commented on SUREFIRE-2065:
----------------------------------------------------

When creating the reports it seems that the need is to have a unique way of identifying the test being executed. If the test executed does not have a unique identifier then other problems would come up (what caused the initial issue here). It would mistakenly consider multiple tests to be one leading to other problems.

I am not 100% sure when this 'displayName' should be used (other than in your IDE when running the tests) ... maybe the log should show with proper display name, but I am still seeing the unique name instead, so this may still be a problem even after this fix

> Test Reports Inconsistencies with Parameterized and junit4
> ----------------------------------------------------------
>
>                 Key: SUREFIRE-2065
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2065
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 3.0.0-M5, 3.0.0-M6, 3.0.0-M7
>            Reporter: Christian Marquez Grabia
>            Priority: Minor
>
> Running parameterized tests with the junit-platform provider causes tests to be counted as single test (unlike using junit4 provider). This makes the tests to be marked as 'Flaky' and marks the build as successful if the retry failed count is greater than zero. Reports also show a single test run even if there were multiple tests with different parameters.
> For a sample project with the problem see [surefire-flaky-issue|https://github.com/chalmagr/surefire-flaky-report] 
> This is also a possibly related to issue SUREFIRE-2010 and may help in the resolution of it.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)