Builder pattern for test data in JUnit - Test Execution Trace

Test Overview

This test uses the Builder pattern to create a User object with test data. It verifies that the User object is built correctly with the expected name and age.

Test Code - JUnit 5

JUnit

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

public class UserTest {

    static class User {
        private final String name;
        private final int age;

        private User(Builder builder) {
            this.name = builder.name;
            this.age = builder.age;
        }

        public String getName() {
            return name;
        }

        public int getAge() {
            return age;
        }

        public static class Builder {
            private String name;
            private int age;

            public Builder setName(String name) {
                this.name = name;
                return this;
            }

            public Builder setAge(int age) {
                this.age = age;
                return this;
            }

            public User build() {
                return new User(this);
            }
        }
    }

    @Test
    public void testUserBuilder() {
        User user = new User.Builder()
                .setName("Alice")
                .setAge(30)
                .build();

        assertEquals("Alice", user.getName());
        assertEquals(30, user.getAge());
    }
}

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts	JUnit test runner is ready	—	PASS
2	Creates User.Builder instance	Builder object with default null name and age 0	—	PASS
3	Calls setName("Alice") on Builder	Builder object with name = "Alice", age = 0	—	PASS
4	Calls setAge(30) on Builder	Builder object with name = "Alice", age = 30	—	PASS
5	Calls build() to create User object	User object created with name = "Alice", age = 30	—	PASS
6	Assert user.getName() equals "Alice"	User object with name = "Alice"	user.getName() == "Alice"	PASS
7	Assert user.getAge() equals 30	User object with age = 30	user.getAge() == 30	PASS
8	Test ends successfully	Test passed	—	PASS

Failure Scenario

Failing Condition: Builder sets incorrect age value or name is null

Execution Trace Quiz - 3 Questions

What does the Builder pattern help with in this test?

A Running the test faster

B Automatically generating test reports

C Creating User objects step-by-step with clear values

D Finding elements on a web page

Key Result

Using the Builder pattern for test data helps create clear, readable, and flexible test objects. It avoids long constructors and makes tests easier to maintain.

Practice

1. What is the main benefit of using the Builder pattern for test data in JUnit tests?

easy

A. It automatically runs tests faster without code changes.

B. It generates random test data without any setup.

C. It replaces the need for assertions in tests.

D. It creates test data with clear, readable, and flexible code.

Solution

1. Step 1: Understand Builder pattern purpose

   The Builder pattern helps create objects step-by-step with readable code.

2. Step 2: Relate to test data creation

   Using Builder for test data makes tests clearer and easier to maintain by avoiding repeated setup code.

3. Final Answer:

   It creates test data with clear, readable, and flexible code. -> Option D

4. Quick Check:

   Builder pattern = clear, flexible test data [OK]

Hint: Builder pattern improves test data clarity and flexibility [OK]

Common Mistakes:

• Thinking Builder speeds up test execution
• Believing Builder removes need for assertions
• Confusing Builder with random data generation

2. Which of the following is the correct way to start a Builder for a User object in JUnit?

easy

A. User user = User.builder().setName("Alice").build();

B. User user = new User.Builder().setName("Alice").build();

C. User user = new User().builder().setName("Alice").build();

D. User user = User.build().setName("Alice").builder();

Solution

1. Step 1: Identify common Builder syntax

   Usually, Builder is started with a static method like builder() on the class.

2. Step 2: Check method chaining order

   Correct chaining is User.builder().setName(...).build(). User user = User.builder().setName("Alice").build(); matches this.

3. Final Answer:

   User user = User.builder().setName("Alice").build(); -> Option A

4. Quick Check:

   Static builder() method starts Builder [OK]

Hint: Start Builder with ClassName.builder() static method [OK]

Common Mistakes:

• Using new User.Builder() instead of User.builder()
• Calling builder() on an instance instead of class
• Mixing build() and builder() order

3. Given this Builder code snippet, what will be the value of user.getAge()?

var user = User.builder()
  .setName("Bob")
  .setAge(30)
  .setAge(25)
  .build();

medium

A. 30

B. 25

C. null

D. Compilation error

Solution

1. Step 1: Analyze method calls order

   The Builder sets age first to 30, then overwrites it to 25 before build.

2. Step 2: Understand final value assignment

   The last call to setAge(25) overwrites previous age, so final age is 25.

3. Final Answer:

   25 -> Option B

4. Quick Check:

   Last setter call wins = 25 [OK]

Hint: Last setter call overwrites previous value [OK]

Common Mistakes:

• Assuming first setAge value remains
• Thinking Builder merges values
• Expecting compilation error due to repeated setters

4. Identify the error in this Builder usage for a Product test data:

var product = Product.builder()
  .setName("Book")
  .setPrice(-10)
  .build();

medium

A. Negative price should be rejected or cause error.

B. Missing call to build() method.

C. Builder must be created with new keyword.

D. setName() cannot be called before setPrice().

Solution

1. Step 1: Check Builder method calls

   Builder calls setName, setPrice, then build() correctly.

2. Step 2: Validate data correctness

   Price is set to -10, which is invalid for product price and should be rejected or throw error.

3. Final Answer:

   Negative price should be rejected or cause error. -> Option A

4. Quick Check:

   Invalid data in Builder = error [OK]

Hint: Check for invalid data values in Builder calls [OK]

Common Mistakes:

• Thinking build() call is missing
• Assuming new keyword is required for Builder
• Believing setter order matters

5. You want to create multiple Order test objects with different status but same customerId and amount. How can you best use the Builder pattern to avoid repeating common fields?

hard

A. Use static variables for common fields and set status directly on Order after build.

B. Write separate Builder calls fully for each Order with all fields repeated.

C. Create a base Builder with common fields, then clone and set different statuses before build.

D. Create Orders with default constructor and set fields manually without Builder.

Solution

1. Step 1: Identify repeated data in test objects

   customerId and amount are same for all Orders; status differs.

2. Step 2: Use Builder cloning or base setup

   Create a base Builder setting common fields, then clone or copy it to set different statuses before building each Order.

3. Final Answer:

   Create a base Builder with common fields, then clone and set different statuses before build. -> Option C

4. Quick Check:

   Reuse Builder base to avoid repetition [OK]

Hint: Reuse Builder base, change only differing fields [OK]

Common Mistakes:

• Repeating all fields in each Builder call
• Setting fields after build instead of in Builder
• Avoiding Builder and using manual setters