[
https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841270#comment-16841270
]
Jonathan Bell commented on SUREFIRE-1584:
-----------------------------------------
Great! If it's OK with you, we would like to make a single PR (with tests) that:
# Adds reruns for JUnit5
# Standardizes reruns for all of the JUnit runners so that the reruns occur in
a new JVM at the end of test execution (as Lamyaa proposed in [PR
102|https://github.com/apache/maven-surefire/pull/102]). We did a case study
and found that the existing rerun mechanism in Surefire (which reruns tests in
the same JVM that they failed in) only found about 25% of the flaky tests that
were found by instead rerunning tests in a new JVM - [details on that
evaluation are here|https://www.deflaker.org/case-studies/].
# Adds timing information for reruns to the XML reports (also as Lamyaa
proposed in [PR 96|https://github.com/apache/maven-surefire/pull/96])
Or, if you would prefer, we can do each of these changes as separate PRs
(reviving the existing PR's 102 and 96; I can discuss and coordinate with
Lamyaa also - we have worked together in the past). If you have any other
suggestions for easy features to implement to simplify/standardize the rerun
mechanism in Surefire, please let us know, we would be happy to contribute more.
> Rerun Failing Tests with JUnit 5
> --------------------------------
>
> Key: SUREFIRE-1584
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1584
> Project: Maven Surefire
> Issue Type: New Feature
> Components: JUnit 5.x support, Maven Surefire Report Plugin
> Affects Versions: 2.22.0
> Reporter: Tic Tac
> Priority: Major
> Labels: junit5
>
> The very useful feature for integration tests ¨[Rerun Failing
> Tests|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]¨
> is currently only supported for the very outdated JUnit 4.
> The documentation says: ¨This feature is supported only for JUnit 4.x.¨
> Can you please support this feature for JUnit 5.3 or later?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
