You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2021/12/17 21:24:00 UTC
[jira] [Commented] (SUREFIRE-1657) `skipAfterFailureCount` not working with JUnit 5
[ https://issues.apache.org/jira/browse/SUREFIRE-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461676#comment-17461676 ]
Slawomir Jaranowski commented on SUREFIRE-1657:
-----------------------------------------------
Can you check with the latest version 3.0.0-M5
> `skipAfterFailureCount` not working with JUnit 5
> ------------------------------------------------
>
> Key: SUREFIRE-1657
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1657
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
> Affects Versions: 2.22.1
> Environment: java version "1.8.0_201"
> Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
> macOS 10.14.3
> Apache Maven 3.6.0
> Reporter: Ion Iovu
> Priority: Major
> Attachments: stop-on-fail.zip
>
>
> Attached MVP demonstrating issue. 2 commits. One showing working example with JUnit 4.12, and another showing reproducing issue with JUnit 5.4. There are 3 failing tests and *skipAfterFailureCount=1* configured.
> *Steps to reproduce*
> # Run _$ mvn clean test_ on attached project
> *Expected*
> After _fail1()_ test method fails, the other two test methods not executed.
> *Actual*
> All 3 methods executed:
> {code:java}
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] MyTest.fail1:12
> [ERROR] MyTest.fail2:17
> [ERROR] MyTest.fail3:22{code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)