Partner – Moderne – NPI EA (cat=Spring Boot)
announcement - icon

Refactor Java code safely — and automatically — with OpenRewrite.

Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.

Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.

Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.

Course – Black Friday 2026 – NPI EA – main – before_post_content
announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW

Course – Black Friday 2026 – NPI – main – before_post_content
announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW

1. Overview

When writing unit tests, we sometimes provide multiple assertions of the output. The test stops when the first of these assertions fail. This means that we don’t find out if any of the later assertions would have passed or failed, which can increase debugging time.

We can solve this problem by wrapping multiple assertions up into a single action.

In this short tutorial, we’ll learn how to use the assertAll() method introduced in JUnit5 and see how it’s different from using multiple assertions.

2. Model

We’ll use a User class to help with our examples:

public class User {
    String username;
    String email;
    boolean activated;
    //constructors
   //getters and setters
}

3. Using Multiple Assertions

Let’s start with an example where all of our assertions would fail:

User user = new User("baeldung", "[email protected]", false);
assertEquals("admin", user.getUsername(), "Username should be admin");
assertEquals("[email protected]", user.getEmail(), "Email should be [email protected]");
assertTrue(user.getActivated(), "User should be activated");

After running the test only the first assertion fails:

org.opentest4j.AssertionFailedError: Username should be admin ==> 
Expected :admin
Actual   :baeldung

Let’s say we fix the failing code or test and re-run the test. We’d then get a second failure, and so on. It would be better, in this situation, to group all these assertions into a single pass/failure.

4. Using the assertAll() Method

We can group assertions with JUnit5 using assertAll().

4.1. Understanding assertAll()

The assertAll() assertion function takes a collection of multiple Executable objects:

assertAll(
  "Grouped Assertions of User",
  () -> assertEquals("baeldung", user.getUsername(), "Username should be baeldung"),
  // more assertions
  ...
 );

We can therefore use lambdas to provide each of our assertions. The lambda will be called to run the assertion within the grouping provided by assertAll().

Here, in the first parameter to assertAll(), we’ve also provided a description to explain the meaning of the whole group.

4.2. Grouping Assertions Using assertAll()

Let’s see the complete example:

User user = new User("baeldung", "[email protected]", false);
assertAll(
  "Grouped Assertions of User",
  () -> assertEquals("admin", user.getUsername(), "Username should be admin"),
  () -> assertEquals("[email protected]", user.getEmail(), "Email should be [email protected]"),
  () -> assertTrue(user.getActivated(), "User should be activated")
);

Now, let’s see what happens when we run the test:

org.opentest4j.MultipleFailuresError: Grouped Assertions of User (3 failures)
org.opentest4j.AssertionFailedError: Username should be admin ==> expected: <admin> but was: <baeldung>
org.opentest4j.AssertionFailedError: Email should be [email protected] ==> expected: <[email protected]> but was: <[email protected]>
org.opentest4j.AssertionFailedError: User should be activated ==> expected: <true> but was: <false>

Contrary to what happened with multiple assertions, this time all the assertions were executed and their failures were reported in the MultipleFailuresError message.

We should note that assertAll() only handles AssertionError. If any assertion were to end with an exception, rather than the usual AssertionError, execution stops immediately and the error output would relate to the exception, rather than MultipleFailuresError.

5. Conclusion

In this article, we learned to use assertAll() in JUnit5 and saw how it’s different than using multiple individual assertions.

The code backing this article is available on GitHub. Once you're logged in as a Baeldung Pro Member, start learning and coding on the project.
Partner – Moderne – NPI EA (tag=Refactoring)
announcement - icon

Modern Java teams move fast — but codebases don’t always keep up. Frameworks change, dependencies drift, and tech debt builds until it starts to drag on delivery. OpenRewrite was built to fix that: an open-source refactoring engine that automates repetitive code changes while keeping developer intent intact.

The monthly training series, led by the creators and maintainers of OpenRewrite at Moderne, walks through real-world migrations and modernization patterns. Whether you’re new to recipes or ready to write your own, you’ll learn practical ways to refactor safely and at scale.

If you’ve ever wished refactoring felt as natural — and as fast — as writing code, this is a good place to start.

Course – Black Friday 2026 – NPI EA – main – after_post_content

announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW

Course – Black Friday 2026 – NPI – main – after_post_content

announcement - icon

Yes, we're now running our Black Friday Sale. All Courses are 33% off until 1st December, 2026 at 17:00 Romania time:

>> EXPLORE ACCESS NOW