Test doubles concept in Ruby - Time & Space Complexity

Time Complexity: Test doubles concept

O(n)

Understanding Time Complexity

When using test doubles, we want to see how the time to run tests changes as the number of doubles grows.

We ask: How does adding more test doubles affect test execution time?

Scenario Under Consideration

Analyze the time complexity of the following Ruby code using test doubles.

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

      def process(order)
        @payment_gateway.charge(order.amount)
      end
    end

    payment_double = double('PaymentGateway')
    allow(payment_double).to receive(:charge).and_return(true)

    processor = OrderProcessor.new(payment_double)
    processor.process(order)
    

This code uses a test double to replace a real payment gateway in order processing.

Identify Repeating Operations

Look for repeated calls or loops involving test doubles.

• Primary operation: Calling the double's method charge.
• How many times: Once per order processed, or once per test run.

How Execution Grows With Input

As the number of test doubles or calls grows, the total calls to doubles grow linearly.

Input Size (number of calls)	Approx. Operations
10	10 calls to doubles
100	100 calls to doubles
1000	1000 calls to doubles

Pattern observation: The number of operations grows directly with the number of calls.

Final Time Complexity

Time Complexity: O(n)

This means the time to run tests grows in a straight line as you add more calls to test doubles.

Common Mistake

[X] Wrong: "Test doubles make tests run instantly, no matter how many calls there are."

[OK] Correct: Each call to a double still takes time, so more calls mean more time, even if faster than real objects.

Interview Connect

Understanding how test doubles affect test speed helps you write efficient tests and explain your choices clearly.

Self-Check

What if we replaced test doubles with real objects that perform network calls? How would the time complexity change?

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