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.