Using the Engine Test Kit in JUnit 5

The JUnit 5 Engine Test Kit provides a way to programmatically run test plans and collect detailed insights about their…

Read More »

Fixing the JUnit Error: One Public Zero-Argument Constructor Required

When working with JUnit—especially JUnit 4—developers often encounter the error: java.lang.Exception: Test class should have exactly one public zero-argument constructor.…

Read More »

JUnit5 TestSuite Alternative

JUnit4 had the TestSuiteclass to aggregate multiple tests. This is not available in JUnit 5. Generally test discovery via a…

Read More »

Possible ways to use Arquillian in Jakarta EE TCKs

Recently, we had a discussion how to create a standalone Jakarta Batch test kit (TCK). For most of the committers,…

Read More »

PIT, JUnit 5 and Gradle – with just one extra line of configuration

Discover dead simple, improved PIT and JUnit 5 configuration in Gradle (with gradle-pitest-plugin 1.4.7+). JUnit 5 is undeniably more and…

Read More »

Migrating Spock 1.3 tests to Spock 2.0

Get know what you can expect from Spock 2.0 M1 (based on JUnit 5), how to migrate to it in…

Read More »

Unit testing DynamoDB applications using JUnit5

In a previous post I had described the new AWS SDK for Java 2 which provides non-blocking IO support for Java…

Read More »

@ParameterizedTest with null values in @CvsSource

Writing parameterized tests in JUnit 4 was pretty cumbersome. JUnit 5 introduced several useful improvements to the framework and running…

Read More »

Blow up Your JUnit5 Tests with Permutations

Writing JUnit tests can be a tedious and boring process. Learn how you can improve your tests classes using permutations…

Read More »