Stub objects in JUnit

Introduction

Stub objects help us test parts of a program by pretending to be other parts. They give fixed answers so we can focus on what we want to test.

When the real part is not ready yet but you want to test your code.

When the real part is slow or hard to use during tests.

When you want to control the answers from a part to test different situations.

When the real part depends on things outside your control, like a database or web service.

Syntax

JUnit

class StubClass implements Interface {
    @Override
    public ReturnType methodName() {
        return fixedValue;
    }
}

Stub classes implement the same interface as the real class.

Methods return fixed values to simulate behavior.

Examples

This stub always returns 5 for add, no matter the inputs.

JUnit

class StubCalculator implements Calculator {
    @Override
    public int add(int a, int b) {
        return 5; // always returns 5
    }
}

This stub returns a fixed user object for any id.

JUnit

class StubUserService implements UserService {
    @Override
    public User getUserById(int id) {
        return new User("TestUser", 123);
    }
}

Sample Program

This test uses a stub calculator that always returns 5 for add. The test checks that the stub returns 5 as expected.

JUnit

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

interface Calculator {
    int add(int a, int b);
}

class StubCalculator implements Calculator {
    @Override
    public int add(int a, int b) {
        return 5; // fixed answer
    }
}

public class CalculatorTest {
    @Test
    void testAddWithStub() {
        Calculator calc = new StubCalculator();
        int result = calc.add(2, 3);
        assertEquals(5, result, "Stub should return fixed value 5");
    }
}

Important Notes

Stubs are simple and return fixed data to help isolate tests.

They are different from mocks, which also check how they are used.

Use stubs to avoid slow or unreliable parts during testing.

Summary

Stub objects replace real parts with fixed answers for testing.

They help test code in isolation and control test conditions.

Stubs are easy to write and useful when real parts are unavailable or slow.

Practice

1. What is the main purpose of a stub object in JUnit testing?

easy

A. To replace a real object with fixed responses for controlled testing

B. To generate random data during test execution

C. To speed up the compilation of test classes

D. To automatically fix bugs found during testing

Solution

1. Step 1: Understand the role of stub objects

   Stub objects are used to replace real parts of a system with simple implementations that return fixed data.

2. Step 2: Identify the purpose in testing

   This allows tests to run in isolation and control the test environment by providing predictable responses.

3. Final Answer:

   To replace a real object with fixed responses for controlled testing -> Option A

4. Quick Check:

   Stub objects = fixed responses for isolation [OK]

Hint: Stub = fixed answers to isolate tests quickly [OK]

Common Mistakes:

• Confusing stubs with mocks or spies
• Thinking stubs generate random data
• Believing stubs fix bugs automatically

2. Which of the following is the correct way to create a simple stub in JUnit using an anonymous class?

easy

A. MyService service = new MyService(); service.getValue() = 5;

B. MyService service = new MyService.getValue(5);

C. MyService service = new MyService() { public int getValue() { return 5; } };

D. MyService service = new MyService() -> 5;

Solution

1. Step 1: Recognize Java anonymous class syntax

   Creating a stub often uses an anonymous class overriding methods to return fixed values.

2. Step 2: Check each option's syntax

   MyService service = new MyService() { public int getValue() { return 5; } }; correctly overrides getValue() to return 5. Options A, C, and D have invalid Java syntax.

3. Final Answer:

   MyService service = new MyService() { public int getValue() { return 5; } }; -> Option C

4. Quick Check:

   Anonymous class override = MyService service = new MyService() { public int getValue() { return 5; } }; [OK]

Hint: Anonymous class overrides method with fixed return [OK]

Common Mistakes:

• Trying to assign a value directly to a method call
• Using incorrect method call syntax
• Confusing lambda syntax with anonymous classes

3. Given the stub below, what will be the output of testService.getValue()?

class TestService {
  int getValue() { return 0; }
}

TestService testService = new TestService() {
  @Override
  int getValue() { return 10; }
};
System.out.println(testService.getValue());

medium

A. Runtime exception

B. 0

C. Compilation error

D. 10

Solution

1. Step 1: Understand method overriding in anonymous class

   The anonymous class overrides getValue() to return 10 instead of 0.

2. Step 2: Determine output of the print statement

   Calling testService.getValue() invokes the overridden method, so it returns 10.

3. Final Answer:

   10 -> Option D

4. Quick Check:

   Overridden method returns 10 [OK]

Hint: Overridden method in stub returns new value [OK]

Common Mistakes:

• Assuming original method runs instead of overridden
• Thinking anonymous class causes compile error
• Expecting runtime exceptions without errors

4. Identify the error in the following stub creation code snippet:

MyService service = new MyService() {
  public int getValue() {
    return "five";
  }
};

medium

A. Cannot override getValue method

B. Method getValue returns wrong data type

C. Missing semicolon after class definition

D. Anonymous class syntax is incorrect

Solution

1. Step 1: Check method return type consistency

   The method getValue() is declared to return int, but returns a String "five".

2. Step 2: Verify syntax correctness

   The anonymous class syntax and semicolon are correct; overriding is allowed.

3. Final Answer:

   Method getValue returns wrong data type -> Option B

4. Quick Check:

   Return type mismatch causes error [OK]

Hint: Return type must match method signature [OK]

Common Mistakes:

• Ignoring return type mismatch
• Assuming syntax error instead of type error
• Thinking overriding is disallowed

5. You want to test a component that depends on a slow external service. Which stub implementation approach is best to speed up tests while ensuring predictable results?

hard

A. Create a stub class that returns fixed, pre-defined data instantly

B. Use the real external service but limit the number of calls

C. Mock the external service to record calls without returning data

D. Skip testing the component until the external service is faster

Solution

1. Step 1: Identify the problem with the real service

   The external service is slow, which slows down tests and makes results unpredictable.

2. Step 2: Choose a stub approach for speed and predictability

   Creating a stub that returns fixed data instantly allows fast, reliable tests without depending on the real service.

3. Step 3: Evaluate other options

   Using the real service or skipping tests delays feedback; mocking without return data doesn't help test results.

4. Final Answer:

   Create a stub class that returns fixed, pre-defined data instantly -> Option A

5. Quick Check:

   Stub fixed data = fast, predictable tests [OK]

Hint: Stub fixed data for fast, reliable tests [OK]

Common Mistakes:

• Using real slow service in tests
• Confusing mocks with stubs
• Skipping tests instead of isolating dependencies