Object Mother pattern in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of the Object Mother pattern

What is the main purpose of using the Object Mother pattern in unit testing with JUnit?

A To mock external dependencies automatically without writing any code

B To centralize and reuse complex test object creation to reduce duplication and improve readability

C To generate random test data for performance testing

D To replace the need for assertions in test methods

💡 Hint

Think about how test objects are created and reused in multiple tests.

The Object Mother pattern helps create and reuse complex test objects in one place, making tests cleaner and easier to maintain.

❓ Predict Output

intermediate

Output of JUnit test using Object Mother

Given the following JUnit test code using an Object Mother, what will be the test result?

JUnit

public class User {
    private String name;
    private int age;
    public User(String name, int age) {
        this.name = name;
        this.age = age;
    }
    public boolean isAdult() {
        return age >= 18;
    }
}

public class UserObjectMother {
    public static User createAdultUser() {
        return new User("Alice", 30);
    }
    public static User createChildUser() {
        return new User("Bob", 10);
    }
}

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

public class UserTest {
    @Test
    public void testAdultUser() {
        User user = UserObjectMother.createAdultUser();
        assertTrue(user.isAdult());
    }
}

A Test passes because the adult user is correctly identified

B Test fails because the age is incorrectly set

C Test fails due to a NullPointerException

D Test fails because the isAdult method is not implemented

💡 Hint

Check the age value and the isAdult method logic.

The Object Mother creates a user with age 30, which is adult. The assertion expects true, so the test passes.

❓ assertion

advanced

Correct assertion for Object Mother created object

Which assertion correctly verifies that a User created by the Object Mother is a child (under 18)?

JUnit

User childUser = UserObjectMother.createChildUser();

A assertTrue(childUser.isAdult());

B assertEquals(true, childUser.isAdult());

C assertNull(childUser);

D assertFalse(childUser.isAdult());

💡 Hint

A child user should not be an adult.

The isAdult method returns false for a child user, so assertFalse correctly verifies this.

🔧 Debug

advanced

Debugging Object Mother test failure

A test using the Object Mother pattern fails with this error: java.lang.AssertionError: expected: but was:. The test code is: User user = UserObjectMother.createAdultUser(); assertTrue(user.isAdult()); What is the most likely cause?

A The assertTrue method is used incorrectly

B The isAdult method always returns false

C The createAdultUser method returns a User with age less than 18

D The User class constructor is missing

💡 Hint

Check the age value set in the Object Mother method.

If createAdultUser returns a user with age under 18, isAdult returns false, causing the assertion to fail.

❓ framework

expert

Best practice for Object Mother usage in JUnit 5

In JUnit 5, which approach best integrates the Object Mother pattern to improve test maintainability and readability?

A Create a separate class with static factory methods for test objects and call them in test methods

B Instantiate test objects directly inside each test method without helpers

C Use @BeforeEach to create all test objects and store them in instance variables

D Use mocking frameworks to replace Object Mother completely

💡 Hint

Think about reusability and clarity of test object creation.

Using a separate class with static methods (Object Mother) centralizes object creation, making tests cleaner and easier to maintain.

Practice

1. What is the main purpose of the Object Mother pattern in JUnit testing?

easy

A. To generate random test data dynamically

B. To create reusable test objects to reduce setup code

C. To mock external services during tests

D. To organize test cases into groups

Solution

1. Step 1: Understand Object Mother role

   The Object Mother pattern provides ready-made objects for tests to avoid repeating setup code.

2. Step 2: Compare with other options

   Mocking services or grouping tests are different patterns; Object Mother focuses on reusable test objects.

3. Final Answer:

   To create reusable test objects to reduce setup code -> Option B

4. Quick Check:

   Object Mother = reusable test objects [OK]

Hint: Object Mother = reusable test objects for simpler tests [OK]

Common Mistakes:

• Confusing Object Mother with mocking frameworks
• Thinking it generates random data automatically
• Believing it organizes test suites

2. Which of the following is the correct way to define an Object Mother method in JUnit for a User object?

easy

A. public User createUser() { return new User("Alice", 30); }

B. User createUser() { return new User("Alice", 30); }

C. public static User createUser() { return new User("Alice", 30); }

D. static User createUser() { return new User("Alice", 30); }

Solution

1. Step 1: Check method signature for Object Mother

   Object Mother methods are usually public static so tests can call them without creating an instance.

2. Step 2: Validate return type and body

   The method returns a new User object with fixed data, matching the pattern.

3. Final Answer:

   public static User createUser() { return new User("Alice", 30); } -> Option C

4. Quick Check:

   Object Mother methods are public static [OK]

Hint: Object Mother methods are public static for easy reuse [OK]

Common Mistakes:

• Omitting static keyword
• Using non-public access modifier
• Missing return type

3. Given this Object Mother method:

public static Order createOrder() {
    return new Order("123", 5, 100.0);
}

What will be the output of this test?

@Test
void testOrderTotal() {
    Order order = ObjectMother.createOrder();
    assertEquals(500.0, order.getTotal());
}

medium

A. Test passes because total is 500.0

B. Test fails because total is 100.0

C. Test fails due to NullPointerException

D. Test fails because order ID is incorrect

Solution

1. Step 1: Calculate expected total from Object Mother data

   Order has quantity 5 and price 100.0, so total = 5 * 100.0 = 500.0.

2. Step 2: Check assertion in test

   The test asserts total equals 500.0, which matches the calculated total.

3. Final Answer:

   Test passes because total is 500.0 -> Option A

4. Quick Check:

   Quantity * Price = Total = 500.0 [OK]

Hint: Multiply quantity and price to find total [OK]

Common Mistakes:

• Assuming total is price only
• Ignoring quantity in calculation
• Expecting NullPointerException without cause

4. Identify the error in this Object Mother method:

public static Product createProduct() {
    Product p = new Product();
    p.setName("Laptop");
    return p;
    p.setPrice(1200);
}

medium

A. Code after return statement is unreachable

B. Missing static keyword in method

C. Product constructor requires parameters

D. Method should return void

Solution

1. Step 1: Analyze method flow

   The return p; line ends the method, so code after it is unreachable.

2. Step 2: Identify unreachable code

   The line p.setPrice(1200); after return will never run, causing a compile warning or error.

3. Final Answer:

   Code after return statement is unreachable -> Option A

4. Quick Check:

   Code after return is unreachable [OK]

Hint: No code runs after return statement [OK]

Common Mistakes:

• Ignoring unreachable code warnings
• Assuming method can run code after return
• Confusing method return type

5. You have multiple tests needing different User objects: one active, one inactive, and one admin. How should you design your Object Mother class to best support this?

hard

A. Use a mocking framework instead of Object Mother

B. Create one method createUser(String type) with if-else inside

C. Create User objects directly in each test without Object Mother

D. Create separate static methods: activeUser(), inactiveUser(), adminUser()

Solution

1. Step 1: Understand Object Mother best practice

   Separate static methods for each test object type keep tests clear and Object Mother simple.

2. Step 2: Compare alternatives

   Using one method with if-else adds complexity; creating objects in tests repeats code; mocking is different purpose.

3. Final Answer:

   Create separate static methods: activeUser(), inactiveUser(), adminUser() -> Option D

4. Quick Check:

   Separate methods = clear reusable objects [OK]

Hint: Use separate methods for each test object type [OK]

Common Mistakes:

• Overloading one method with many conditions
• Not using Object Mother and repeating code
• Confusing mocking with object creation