Test doubles concept in Ruby

Introduction

Test doubles help you pretend parts of your program work in a simple way so you can test other parts easily.

When you want to test a part of your program without using a real database.

When a part of your program talks to an external service like a website or API.

When you want to check if a method was called without running its real code.

When the real part is slow or hard to set up for testing.

When you want to control what a method returns during a test.

Syntax

Ruby

double('Name', method_name: return_value)
allow(double).to receive(:method_name).and_return(return_value)

double('Name') creates a fake object with a name for clarity.

You can set methods and their return values directly or use allow to set expectations.

Examples

This creates a fake user object that returns 'Alice' when you ask for its name.

Ruby

user = double('User', name: 'Alice')
puts user.name  # prints 'Alice'

This sets up a fake calculator where the add method always returns 5, no matter the input.

Ruby

calculator = double('Calculator')
allow(calculator).to receive(:add).and_return(5)
puts calculator.add(2, 3)  # prints 5

Sample Program

This program uses a test double to fake a payment gateway. It checks that when pay is called, the fake gateway's charge method returns 'Success'.

Ruby

require 'rspec/mocks/standalone'

class Order
  def initialize(payment_gateway)
    @payment_gateway = payment_gateway
  end

  def pay(amount)
    @payment_gateway.charge(amount)
  end
end

# Create a test double for payment_gateway
payment_gateway = double('PaymentGateway')

# Tell the double to expect charge and return 'Success'
allow(payment_gateway).to receive(:charge).with(100).and_return('Success')

order = Order.new(payment_gateway)
result = order.pay(100)
puts result

Important Notes

Test doubles do not run real code, so they make tests faster and simpler.

Use descriptive names for doubles to keep tests clear.

You can check if methods were called on doubles to verify behavior.

Summary

Test doubles let you replace real parts with simple fake ones for testing.

They help isolate the part you want to test without outside effects.

You can control what doubles return and check how they are used.

Practice

1.

What is the main purpose of using test doubles in Ruby testing?

easy

A. To permanently change the behavior of classes

B. To speed up the program execution in production

C. To replace real objects with fake ones to isolate tests

D. To automatically generate user interface elements

Solution

1. Step 1: Understand what test doubles do

   Test doubles are fake objects used in tests to replace real parts of the program.

2. Step 2: Identify the main goal

   The goal is to isolate the part being tested by removing outside effects from real objects.

3. Final Answer:

   To replace real objects with fake ones to isolate tests -> Option C

4. Quick Check:

   Test doubles isolate tests = A [OK]

Hint: Test doubles fake objects to isolate tests quickly [OK]

Common Mistakes:

• Thinking test doubles speed up production code
• Believing test doubles permanently change classes
• Confusing test doubles with UI tools

2.

Which of the following is the correct way to create a test double named user in Ruby using RSpec?

?

easy

A. user = fake('user')

B. user = double('user')

C. user = stub('user')

D. user = mock_object('user')

Solution

1. Step 1: Recall RSpec syntax for test doubles

   RSpec uses the method double to create test doubles.

2. Step 2: Match the correct method call

   The correct syntax is double('name'), so double('user') is right.

3. Final Answer:

   user = double('user') -> Option B

4. Quick Check:

   RSpec double creation = A [OK]

Hint: Use double('name') to create test doubles in RSpec [OK]

Common Mistakes:

• Using fake or stub instead of double
• Confusing mock_object with double
• Missing quotes around the name

3.

What will be the output of this Ruby code using a test double?

user = double('user')
allow(user).to receive(:name).and_return('Alice')
puts user.name

medium

A. Alice

B. nil

C. user

D. NoMethodError

Solution

1. Step 1: Understand the double setup

   The double user is told to respond to name with 'Alice'.

2. Step 2: Check the method call output

   Calling user.name returns 'Alice' as set by and_return.

3. Final Answer:

   Alice -> Option A

4. Quick Check:

   Double returns stubbed value = C [OK]

Hint: Stub method with and_return to control output [OK]

Common Mistakes:

• Expecting the double name instead of stubbed return
• Thinking it returns nil by default
• Assuming NoMethodError without stub

4.

Identify the error in this test double usage and how to fix it:

order = double('order')
allow(order).to receive(:total)
puts order.total

medium

A. Missing and_return causes order.total to return nil, fix by adding and_return

B. Double name should be a symbol, fix by using double(:order)

C. Cannot call allow on a double, fix by using expect

D. Missing puts before order.total

Solution

1. Step 1: Analyze the stub setup

   The method total is allowed but no return value is set, so it returns nil.

2. Step 2: Fix by adding return value

   Add and_return(value) to specify what total should return.

3. Final Answer:

   Missing and_return causes order.total to return nil, fix by adding and_return -> Option A

4. Quick Check:

   Stub needs return value = B [OK]

Hint: Always add and_return to stub methods for expected output [OK]

Common Mistakes:

• Thinking double name must be symbol
• Confusing allow with expect usage
• Forgetting to print output

5.

You want to test a PaymentProcessor class that calls an external Gateway service. How can you use a test double to ensure your test does not call the real Gateway?

class PaymentProcessor
  def initialize(gateway)
    @gateway = gateway
  end

  def pay(amount)
    @gateway.charge(amount)
  end
end

# Test code here?

hard

A. Remove the gateway parameter and hardcode the call inside PaymentProcessor

B. Call the real Gateway class directly in the test

C. Use allow_any_instance_of(Gateway) to stub charge

D. Create a double for gateway that expects charge with amount and returns true

Solution

1. Step 1: Understand dependency injection

   The PaymentProcessor takes a gateway object to call charge.

2. Step 2: Use a test double for gateway

   Create a double that expects charge with the amount and returns true to simulate success.

3. Step 3: Avoid calling real external service

   This prevents the test from calling the real Gateway, isolating the test.

4. Final Answer:

   Create a double for gateway that expects charge with amount and returns true -> Option D

5. Quick Check:

   Use doubles to isolate external calls = D [OK]

Hint: Inject doubles to replace external services in tests [OK]

Common Mistakes:

• Calling real external services in tests
• Hardcoding dependencies inside classes
• Using allow_any_instance_of unnecessarily