Introduction to Mocks with Ruby and RSpec

In our journey through isolating dependencies with test doubles, we've explored dummies, stubs, and spies. This lesson focuses on mocks, a powerful type of test double used in Ruby to simulate external dependencies in software tests. You may have noticed in the previous unit how spying on the real implementation can become cumbersome. Mocks can imitate the behavior of complex systems, allowing us to test code in isolation without relying on real, unpredictable systems like databases or web services.

Now, let's review the TDD workflow:

• Red: Write a failing test.
• Green: Write the minimum code to pass the test.
• Refactor: Improve the code structure without changing its behavior.

We'll demonstrate these principles using mocks, helping you effectively isolate and test your application logic.

Mocks are indispensable in TDD because they allow you to test your code independently of the parts of the system you don't control. For example, when writing tests for a PricingService, you don't want the tests to fail due to external issues like a currency conversion API being down. Mocks provide a controlled environment where you can simulate various conditions and responses as well as validate the calls.

Mocks differ from spies in that they fully simulate dependencies rather than just observing behavior. A mock creates a controlled substitute for a dependency, ensuring that actual code or functionality isn't executed. For instance, if a function interacts with an external API, a mock can simulate different responses from that API without making a network request.

Let's dive into mocking with RSpec. We'll start with the basics: how to mock a class and its methods in Ruby.

Consider the ExchangeRateService, which fetches exchange rates from an API. In testing the PricingService, we need to mock this service to ensure our tests don't rely on actual API responses.

Here's a simple way to mock with RSpec:

# In spec/pricing_service_spec.rb
RSpec.describe PricingService do
  # Create a mock double for the ExchangeRateService
  let(:mock_exchange_rate_service) { double("ExchangeRateService") }
  
  # Instantiate PricingService with the mock ExchangeRateService
  let(:pricing_service) { PricingService.new(mock_exchange_rate_service) }

  it 'converts prices using exchange rate' do
    # Arrange: Set up the mock to return a specific value when get_rate is called
    allow(mock_exchange_rate_service).to receive(:get_rate).with('USD', 'EUR').and_return(1.5)

    # Act: Call the method under test
    result = pricing_service.convert_price(100.0, "USD", "EUR")

    # Assert: Check that get_rate was called once and verify the result
    expect(mock_exchange_rate_service).to have_received(:get_rate).with('USD', 'EUR').once
    expect(result).to eq(150.00)
  end
end

In this setup:

• We use double to create a mock version of the ExchangeRateService.
• allow(mock_exchange_rate_service).to receive is used to control the return value of the method we're simulating.

This approach ensures that tests are decoupled from external systems.