Argument aggregation in JUnit - Build an Automation Script

Test multiple assertions with argument aggregation in JUnit

Preconditions (2)

Step 1: Call add(2, 3) and verify the result is 5

Step 2: Call add(-1, 1) and verify the result is 0

Step 3: Call add(0, 0) and verify the result is 0

Step 4: Use argument aggregation to run all assertions together

✅ Expected Result: All assertions run and failures (if any) are reported together

Automation Requirements - JUnit 5

Assertions Needed:

assertEquals for each add method call

use assertAll to aggregate assertions

Best Practices:

Use assertAll to group related assertions

Write clear assertion messages

Keep test methods focused and readable

Automated Solution

JUnit

import static org.junit.jupiter.api.Assertions.*;
import org.junit.jupiter.api.Test;

class Calculator {
    public int add(int a, int b) {
        return a + b;
    }
}

public class CalculatorTest {

    private final Calculator calculator = new Calculator();

    @Test
    void testAddWithArgumentAggregation() {
        assertAll("Addition tests",
            () -> assertEquals(5, calculator.add(2, 3), "2 + 3 should be 5"),
            () -> assertEquals(0, calculator.add(-1, 1), "-1 + 1 should be 0"),
            () -> assertEquals(0, calculator.add(0, 0), "0 + 0 should be 0")
        );
    }
}

This test class defines a simple Calculator with an add method.

The test method testAddWithArgumentAggregation uses assertAll to group three assertions. Each assertion checks the add method with different inputs.

Using assertAll means all assertions run even if some fail, and the test report shows all failures together. This helps find multiple issues in one test run.

Clear messages in assertions help understand which case failed.

Common Mistakes - 3 Pitfalls

Not using assertAll and writing multiple separate assertions

Using assertAll but passing null or empty lambda expressions

Writing unclear or missing assertion messages

Bonus Challenge

Now add data-driven testing with 3 different input pairs and expected sums using @ParameterizedTest

Show Hint