[jira] [Commented] (SUREFIRE-1584) Rerun Failing Tests with JUnit 5

["Vladimir (JIRA)" <ji...@apache.org>]

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

Vladimir commented on SUREFIRE-1584:
------------------------------------

We have a sizable set of end-to-end browser UI tests currently running on JUnit 4 with Jenkins CI.
This type of tests is inherently flakier than unit tests because of things like network timeouts, browser crashes and other random factors arising from the complexity of testing big systems end-to-end, and not due to specific test problems.
In our case, even if the native JUnit feature is implemented, it would not be the ideal solution as it seems it would target more marking specific tests as flaky. For this reason I find the current surefire.rerunFailingTestsCount=1 option very valuable.
It also works very well with the [Allure|https://docs.qameta.io/allure/] framework, which we use for test reporting and it has built-in support for reruns. We are interested in migrating to JUnit 5, however the lack of rerun support will likely keep us on 4 for now.

> 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)