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

Practice

1. What is the main purpose of using @ArgumentsAggregator in JUnit parameterized tests?

easy

A. To combine multiple method arguments into a single object for easier testing

B. To run tests in parallel threads

C. To generate random test data automatically

D. To skip certain test cases during execution

Solution

1. Step 1: Understand the role of @ArgumentsAggregator

   This annotation is used to create a custom aggregator that combines multiple input arguments into one object.

2. Step 2: Recognize the benefit in parameterized tests

   Aggregating arguments simplifies test method signatures and improves readability by passing one object instead of many parameters.

3. Final Answer:

   To combine multiple method arguments into a single object for easier testing -> Option A

4. Quick Check:

   @ArgumentsAggregator = combine inputs [OK]

Hint: Remember: Aggregator groups inputs into one object [OK]

Common Mistakes:

• Confusing @ArgumentsAggregator with parallel test execution
• Thinking it generates test data automatically
• Assuming it skips tests

2. Which of the following is the correct way to apply a custom aggregator in a JUnit 5 parameterized test method parameter?

easy

A. @AggregateWith(CustomAggregator.class) MyObject obj

B. @ArgumentsSource(CustomAggregator.class) MyObject obj

C. @AggregateArguments(CustomAggregator.class) MyObject obj

D. @ArgumentAggregator(CustomAggregator.class) MyObject obj

Solution

1. Step 1: Recall the correct annotation for applying aggregators

   The annotation to apply a custom aggregator on a parameter is @AggregateWith.

2. Step 2: Match the syntax

   The correct syntax is @AggregateWith(CustomAggregator.class) followed by the parameter type and name.

3. Final Answer:

   @AggregateWith(CustomAggregator.class) MyObject obj -> Option A

4. Quick Check:

   @AggregateWith = apply aggregator [OK]

Hint: Use @AggregateWith to link aggregator class to parameter [OK]

Common Mistakes:

• Using @ArgumentsSource instead of @AggregateWith
• Misspelling the annotation name
• Confusing @AggregateWith with @ArgumentAggregator

3. Given the following aggregator implementation and test method, what will be the output of the assertion?

public class PersonAggregator implements ArgumentsAggregator {
  @Override
  public Person aggregateArguments(ArgumentsAccessor accessor, ParameterContext context) {
    return new Person(accessor.getString(0), accessor.getInteger(1));
  }
}

@ParameterizedTest
@CsvSource({"Alice,30", "Bob,25"})
void testPerson(@AggregateWith(PersonAggregator.class) Person person) {
  assertTrue(person.getAge() > 20);
}

medium

A. Test fails for Alice because age is 30

B. Test fails for Bob because age is 25

C. Test passes for both Alice and Bob

D. Test fails for both because age is not checked correctly

Solution

1. Step 1: Understand the aggregator behavior

   The aggregator creates a Person object with name and age from CSV input.

2. Step 2: Evaluate the assertion for each input

   Both Alice (30) and Bob (25) have ages greater than 20, so assertTrue(person.getAge() > 20) passes for both.

3. Final Answer:

   Test passes for both Alice and Bob -> Option C

4. Quick Check:

   Age > 20 for both inputs = pass [OK]

Hint: Check each input value against assertion condition [OK]

Common Mistakes:

• Assuming 25 is less than or equal to 20
• Confusing assertion logic
• Ignoring aggregator mapping

4. Identify the error in this aggregator implementation:

public class ProductAggregator implements ArgumentsAggregator {
  @Override
  public Product aggregateArguments(ArgumentsAccessor accessor, ParameterContext context) {
    String name = accessor.getString(0);
    int price = accessor.getInteger(1);
    return new Product(name, price);
  }
}

@ParameterizedTest
@CsvSource({"Laptop,1000", "Phone,abc"})
void testProduct(@AggregateWith(ProductAggregator.class) Product product) {
  assertNotNull(product);
}

medium

A. The aggregator method signature is incorrect

B. The Product constructor parameters are in wrong order

C. The @AggregateWith annotation is missing

D. The second CSV input 'Phone,abc' causes a runtime error due to invalid integer

Solution

1. Step 1: Analyze CSV input and aggregator code

   The second CSV line has 'abc' where an integer price is expected.

2. Step 2: Understand the impact on aggregation

   Calling accessor.getInteger(1) on 'abc' will throw a runtime exception (NumberFormatException).

3. Final Answer:

   The second CSV input 'Phone,abc' causes a runtime error due to invalid integer -> Option D

4. Quick Check:

   Invalid integer input = runtime error [OK]

Hint: Check CSV data types match aggregator expectations [OK]

Common Mistakes:

• Ignoring invalid CSV data causing exceptions
• Assuming aggregator method signature is wrong
• Thinking annotation is missing

5. You want to test a method that takes a Person object with fields name and age. You have CSV data with columns name, age, and city. How can you write a custom aggregator to ignore the city column and only aggregate name and age into Person?

hard

A. Use @AggregateWith but do not implement ArgumentsAggregator interface

B. Use ArgumentsAccessor to get only the first two columns and create Person ignoring city

C. Use @CsvSource with only two columns to avoid city

D. Use ArgumentsAccessor to get all three columns and pass city to Person constructor

Solution

1. Step 1: Understand the CSV data and Person constructor

   CSV has three columns but Person only needs name and age.

2. Step 2: Implement aggregator to pick only needed columns

   Use ArgumentsAccessor.getString(0) and getInteger(1) to get name and age, ignoring the third city column.

3. Final Answer:

   Use ArgumentsAccessor to get only the first two columns and create Person ignoring city -> Option B

4. Quick Check:

   Pick needed columns only in aggregator [OK]

Hint: Pick only needed columns with ArgumentsAccessor [OK]

Common Mistakes:

• Trying to pass extra columns to Person constructor
• Changing CSV source instead of aggregator logic
• Not implementing ArgumentsAggregator interface