Object Mother pattern in JUnit - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Object Mother pattern in testing?

It is a design pattern that creates reusable methods to build test objects with default data, making tests easier to write and read.

beginner

Why use the Object Mother pattern instead of creating objects directly in tests?

Because it reduces duplicate code, centralizes test object creation, and makes tests cleaner and easier to maintain.

intermediate

Show a simple example of an Object Mother method in Java using JUnit.

public class UserObjectMother {
    public static User createDefaultUser() {
        return new User("Alice", "[e-mail]", 30);
    }
}

intermediate

How does the Object Mother pattern improve test readability?

By giving meaningful names to object creation methods, tests read like sentences and focus on behavior, not setup details.

advanced

What is a potential downside of the Object Mother pattern?

If not managed well, it can grow large and complex, making it hard to understand which data is used in tests.

What is the main purpose of the Object Mother pattern?

A To replace unit tests with integration tests

B To mock external services in tests

C To generate random test data at runtime

D To create reusable test objects with default data

The Object Mother pattern focuses on creating reusable test objects with default data to simplify test setup.

Which of the following is a benefit of using Object Mother pattern?

A Centralizes test object creation

B Makes tests harder to read

C Increases duplicate code in tests

D Removes the need for assertions

Centralizing test object creation reduces duplication and improves maintainability.

In JUnit, where would you typically place Object Mother classes?

A In the production database

B Inside the main application source folder

C In the test source folder alongside tests

D In the build configuration files

Object Mother classes belong in the test source folder because they support test code only.

What should Object Mother methods return?

A Null values to simulate errors

B Test objects with default or common data

C Strings describing test cases

D Test reports

They return test objects pre-filled with default or typical data for reuse.

Which is NOT a good practice when using Object Mother pattern?

A Creating one huge Object Mother with all test data

B Giving methods descriptive names

C Keeping Object Mother classes small and focused

D Using Object Mother to reduce test setup code

Creating one huge Object Mother class can make maintenance difficult and reduce clarity.

Explain the Object Mother pattern and how it helps in writing unit tests.

Think about how you prepare objects for many tests without repeating code.

Describe a simple example of an Object Mother method in Java and how you would use it in a JUnit test.

Imagine a method that creates a user with default info for tests.

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