[
https://issues.apache.org/jira/browse/SUREFIRE-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543773#comment-17543773
]
Aaron Braunstein commented on SUREFIRE-2065:
--------------------------------------------
This issue also causes @ParameterizedTest
[name|https://junit.org/junit5/docs/current/api/org.junit.jupiter.params/org/junit/jupiter/params/ParameterizedTest.html#name()]
to have no effect in junit 5 tests right?
{code:java}
public static Stream<String> params() {
return Stream.of("Hello World");
}
@ParameterizedTest(name = "{index}: {0}")
@MethodSource("params")
public void test(String param) {} {code}
Expected: test(String)[1: Hello World]
Actual: test(String)[1]
> 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)
