Dummy objects in JUnit - Test Execution Trace

Test Overview

This test demonstrates the use of a dummy object in JUnit. It verifies that a method can be called with a dummy parameter without affecting the test outcome.

Test Code - JUnit

JUnit

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

class UserService {
    void registerUser(User user) {
        // Registration logic here
    }
}

class User {
    String name;
    User(String name) { this.name = name; }
}

public class DummyObjectTest {
    @Test
    void testRegisterUserWithDummy() {
        UserService service = new UserService();
        User dummyUser = new User("dummy"); // Dummy object
        service.registerUser(dummyUser);
        // No assertion needed as dummy is just a placeholder
        assertTrue(true); // To mark test as passed
    }
}

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Test starts	JUnit test runner initialized	-	PASS
2	UserService instance created	UserService object ready for use	-	PASS
3	Dummy User object created with name 'dummy'	User object exists but not used for logic	-	PASS
4	registerUser method called with dummy User	Method executed without error	-	PASS
5	Assert true to mark test as passed	Test framework records success	assertTrue(true) passes	PASS

Failure Scenario

Failing Condition: registerUser method throws an exception when called with dummy User

Execution Trace Quiz - 3 Questions

What is the purpose of the dummy User object in this test?

A To act as a placeholder parameter without affecting test logic

B To verify the User's name is stored correctly

C To test the registration logic with real user data

D To cause the test to fail intentionally

Key Result

Use dummy objects as simple placeholders when the parameter is required but not used in the test logic. This keeps tests focused and avoids unnecessary complexity.