Why Test doubles concept in Ruby? - Purpose & Use Cases

The Big Idea

What if you could test your code without waiting for slow or tricky parts every time?

The Scenario

Imagine you are testing a car's braking system, but you have to test it on a real car every time. You need the car, the road, and a safe place to stop. This is like testing code that depends on other parts that are hard to use or slow.

The Problem

Testing with real parts can be slow, risky, and sometimes impossible. You might wait a long time for a response or cause errors that are hard to fix. It's like waiting for a friend to answer the phone every time you want to talk.

The Solution

Test doubles act like pretend parts or friends. They stand in for the real things during tests, so you can check your code quickly and safely without needing the real parts every time.

Before vs After

✗ Before

real_car.brake
assert real_car.stopped?

✓ After

fake_car = TestDouble.new
fake_car.brake
assert fake_car.stopped?

What It Enables

It lets you test your code faster and more reliably by using simple stand-ins instead of the real, complex parts.

Real Life Example

When building a website that sends emails, you don't want to send real emails every time you test. Using test doubles, you can pretend to send emails and check if your code tries to send them correctly.

Key Takeaways

Manual testing with real parts is slow and risky.

Test doubles replace real parts with simple stand-ins.

This makes testing faster, safer, and easier to control.