[
https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841327#comment-16841327
]
Jonathan Bell commented on SUREFIRE-1584:
-----------------------------------------
We are quite familiar with the existing rerun option (which reruns failing test
methods in the same JVM that they had failed in). We have already implemented
the rerun version that I've described above (where failing test methods are
rerun in a _new_ JVM), and found it to be much more effective than the way that
Surefire reruns tests right now ([details and graph
here|https://www.deflaker.org/case-studies/]. Here is a graph showing the
number of tests that originally failed, but eventually passed when rerun,
comparing between Surefire's current rerun mechanism (rerunning failed tests in
the same JVM) and our approach (rerunning failed tests in a new JVM).
!FlakyReruns.png!
We would like to standardize the rerun options to behave the same between all
of the JUnit providers (so that users don't get confused by features that
behave differently for JUnit4/JUnit47/Junit5). So, we would like to implement
either a single rerun failing tests feature that reruns tests in a new JVM
(modifying the existing feature from Qingzhou and Andreas), or add a new option
(to all of the JUnit providers) to rerun failing tests in a new JVM.
> 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
> Attachments: FlakyReruns.png
>
>
> 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)
