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.