Argument aggregation in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of JUnit test with argument aggregation

Consider the following JUnit 5 test using @CsvSource and argument aggregation. What will be the output when the test runs?

JUnit

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.CsvSource;
import org.junit.jupiter.params.aggregator.AggregateWith;
import static org.junit.jupiter.api.Assertions.*;

class User {
    String name;
    int age;
    User(String name, int age) {
        this.name = name;
        this.age = age;
    }
}

class UserAggregator implements org.junit.jupiter.params.aggregator.ArgumentsAggregator {
    @Override
    public User aggregateArguments(org.junit.jupiter.params.aggregator.ArgumentsAccessor accessor, java.lang.reflect.Parameter parameter) {
        return new User(accessor.getString(0), accessor.getInteger(1));
    }
}

public class UserTest {
    @ParameterizedTest
    @CsvSource({"Alice,30", "Bob,25"})
    void testUser(@AggregateWith(UserAggregator.class) User user) {
        assertNotNull(user.name);
        assertTrue(user.age > 20);
    }
}

A Test passes for both Alice and Bob

B Test fails for Alice because age is not > 20

C Test fails for Bob because name is null

D Test throws a runtime exception due to aggregator error

💡 Hint

Think about how the aggregator converts CSV input into User objects and what the assertions check.

The aggregator correctly creates User objects from the CSV input. Both users have non-null names and ages greater than 20, so all assertions pass.

❓ assertion

intermediate

Identify failing assertion in argument aggregation test

Given a parameterized test using argument aggregation, which assertion will fail if the aggregator incorrectly maps parameters?

JUnit

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

class Product {
    String id;
    double price;
    Product(String id, double price) {
        this.id = id;
        this.price = price;
    }
}

// Aggregator maps first param to price, second to id (incorrect)
class ProductAggregator implements org.junit.jupiter.params.aggregator.ArgumentsAggregator {
    @Override
    public Product aggregateArguments(org.junit.jupiter.params.aggregator.ArgumentsAccessor accessor, java.lang.reflect.Parameter parameter) {
        return new Product(accessor.getString(1), accessor.getDouble(0));
    }
}

@org.junit.jupiter.params.ParameterizedTest
@org.junit.jupiter.params.provider.CsvSource({"19.99, P123", "5.50, P456"})
void testProduct(@org.junit.jupiter.params.aggregator.AggregateWith(ProductAggregator.class) Product product) {
    assertNotNull(product.id);
    assertTrue(product.price > 0);
}

A assertNotNull(product.id) fails

B assertTrue(product.price > 0) fails

C Test throws NullPointerException

D Both assertions pass

💡 Hint

Check how the aggregator swaps parameters and what values are passed.

Although the aggregator swaps parameters, the CSV source provides price first and id second, so product.id gets the string id and product.price gets the double price correctly. Both assertions pass.

🔧 Debug

advanced

Debug failing argument aggregation test due to missing parameter

A parameterized test using argument aggregation fails with an IndexOutOfBoundsException. What is the most likely cause?

JUnit

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

@org.junit.jupiter.params.ParameterizedTest
@org.junit.jupiter.params.provider.CsvSource({"John", "Jane, 28"})
void testPerson(@org.junit.jupiter.params.aggregator.AggregateWith(PersonAggregator.class) Person person) {
    assertNotNull(person.name);
    assertTrue(person.age > 0);
}

class Person {
    String name;
    int age;
    Person(String name, int age) {
        this.name = name;
        this.age = age;
    }
}

class PersonAggregator implements org.junit.jupiter.params.aggregator.ArgumentsAggregator {
    @Override
    public Person aggregateArguments(org.junit.jupiter.params.aggregator.ArgumentsAccessor accessor, java.lang.reflect.Parameter parameter) {
        return new Person(accessor.getString(0), accessor.getInteger(1));
    }
}

A The first CSV line has missing age parameter causing IndexOutOfBoundsException

B PersonAggregator class is not public causing reflection failure

C The test method is missing @Test annotation

D Person constructor parameters are in wrong order

💡 Hint

Look at the CSV input lines and how many parameters each has.

The first CSV line has only one parameter (name), but the aggregator expects two parameters (name and age). Trying to access the second parameter causes IndexOutOfBoundsException.

❓ framework

advanced

Best practice for argument aggregation in JUnit 5

Which practice is recommended when implementing a custom ArgumentsAggregator in JUnit 5?

A Throw RuntimeException inside aggregateArguments to fail tests on invalid input

B Use instance variables in the aggregator to store state between test runs

C Make the aggregator class a static nested class or top-level class to avoid reflection issues

D Use @BeforeEach to initialize aggregator fields before each aggregation

💡 Hint

Think about how JUnit uses reflection to instantiate aggregators.

JUnit requires aggregators to be static nested or top-level classes so it can instantiate them via reflection without needing an instance of the outer class. Using instance variables or lifecycle methods is not recommended.

🧠 Conceptual

expert

Understanding argument aggregation behavior with nested objects

In JUnit 5, when using argument aggregation to create a complex object with nested objects, which statement is true?

A JUnit automatically aggregates nested objects if their aggregators are registered globally

B You must manually aggregate nested objects inside the main aggregator; JUnit does not recursively aggregate nested parameters

C Nested objects cannot be used with argument aggregation and require separate parameterized tests

D JUnit uses reflection to automatically instantiate nested objects without custom aggregators

💡 Hint

Consider how argument aggregation works with complex parameter types.

JUnit's argument aggregation works at the top level and does not recursively aggregate nested objects. You must manually create nested objects inside your aggregator implementation.

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