Skip to content

Releases: tginsberg/junit5-system-exit

Release 1.1.2

28 Nov 00:25
Compare
Choose a tag to compare

This release fixes a bug (#12) that makes this library work better with JUnit Parameterized Tests. Thanks to @felix-seifert for the report.

Maven:

<dependency>
    <groupId>com.ginsberg</groupId>
    <artifactId>junit5-system-exit</artifactId>
    <version>1.1.2</version>
    <scope>test</scope>
</dependency

Gradle:

testImplementation("com.ginsberg:junit5-system-exit:1.1.2")

Release 1.1.1

21 Feb 15:40
dadd91e
Compare
Choose a tag to compare

This is a bugfix release to correct issues around @FailOnSystemExit.

Thanks to @eric-unc for finding my bugs! 🙏

Maven:

<dependency>
    <groupId>com.ginsberg</groupId>
    <artifactId>junit5-system-exit</artifactId>
    <version>1.1.1</version>
    <scope>test</scope>
</dependency

Gradle:

testImplementation("com.ginsberg:junit5-system-exit:1.1.1")

Release 1.1.0

20 Feb 23:41
1cfad74
Compare
Choose a tag to compare

Note: There is a bug in this release, please use version 1.1.1 instead!


Release 1.1.0 of junit5-system-exit contains two changes to make testing code that may call System.exit() easier.

🏆 Changes

This release contains the following merged pull requests:

#5 - Make SystemExitPreventedException public and add a statusCode getter
This should help with testing CLIs.

#6 - Add new @FailOnSystemExit annotation
When a test calls System.exit() the JVM running the test will terminate (in most setups). Annotating a test with @FailOnSystemExit will catch this condition and fail the test, rather than exiting the JVM the test is executing on.

🙏 Thanks!

Thank you to @alexanderabramov and @eric-unc for the suggestions!