You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chris Yee (Jira)" <ji...@apache.org> on 2019/12/20 02:08:00 UTC
[jira] [Commented] (SUREFIRE-1739) Regression - Failsafe with JUnit
5: @BeforeAll failure incorrectly succeeds
[ https://issues.apache.org/jira/browse/SUREFIRE-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000554#comment-17000554 ]
Chris Yee commented on SUREFIRE-1739:
-------------------------------------
I searched for a previous issue on this but somehow missed at least two previously reported issues, including https://issues.apache.org/jira/browse/SUREFIRE-1688. So this can be closed as a duplicate. My apologies.
> Regression - Failsafe with JUnit 5: @BeforeAll failure incorrectly succeeds
> ---------------------------------------------------------------------------
>
> Key: SUREFIRE-1739
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1739
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 3.0.0-M4
> Reporter: Chris Yee
> Priority: Major
> Labels: regression
> Attachments: ExampleIT.java, bug_example.tgz, pom.xml
>
>
> A failure in a JUnit 5 @BeforeAll setup method causes the integration tests to be skipped, and the result is an incorrect build success.
> This is a regression; the same code correctly causes a build failure in 2.22.2, 3.0.0-M1, 3.0.0-M2, and 3.0.0-M3.
> Replication steps:
> # Unpack project
> # {{mvn verify}}
> Expected result: Build failure
> Actual result: Build success
> The stdout summary reports that no tests were run
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)