Fake Pattern — Lightweight Working Implementation

In this tutorial, you'll learn how the Fake pattern provides a lightweight but functional implementation of a dependency for testing.

What You'll Learn

how the Fake pattern provides a lightweight but functional implementation of a dependency for testing.

Why It Matters

Stubs are too simple for integration tests. Fakes provide real behavior without heavyweight dependencies.

Real-World Use

In-memory database, fake file system, fake SMTP server, and fake HTTP client.

The Fake Pattern

The Fake pattern addresses a specific recurring design problem by providing a reusable solution structure. Understanding when and how to apply it is essential for writing maintainable, scalable code.

Key Concepts

• Isolation: Testing units independently of dependencies.
• Control: Simulating specific conditions and edge cases.
• Verification: Asserting interactions occurred as expected.
• Coverage: Ensuring all code paths are exercised.

Structure

The following diagram shows the structure of this pattern:

flowchart LR
    Test --> Fake
    Fake -->|stub| Service
    Fake -->|mock verify| Repository

Implementation

from typing import List
from dataclasses import dataclass
from unittest.mock import Mock

@dataclass
class User:
    id: int
    name: str
    is_active: bool = True

class UserService:
    def __init__(self, repo):
        self._repo = repo

    def get_active_users(self) -> List[User]:
        return [u for u in self._repo.find_all() if u.is_active]

# Test with Fake
def test_get_active_users():
    mock_repo = Mock()
    mock_repo.find_all.return_value = [
        User(id=1, name="Alice", is_active=True),
        User(id=2, name="Bob", is_active=False),
        User(id=3, name="Charlie", is_active=True),
    ]
    service = UserService(mock_repo)
    result = service.get_active_users()
    assert len(result) == 2
    assert result[0].name == "Alice"
    assert result[1].name == "Charlie"
    print("Test passed!")

test_get_active_users()

Expected output:

Test passed!

Key Participants

• Client: Code that uses the Fake.
• Fake: The main abstraction provided by the pattern.
• Implementation: Concrete realization of the pattern.
• Data/State: Information managed by the pattern.

Real-World Examples

• DodaTech uses this pattern internally for consistent cross-cutting concerns.
• Major frameworks and libraries implement this pattern as a core architectural element.
• Production systems at scale depend on this pattern for reliability.

Related Patterns

• Mock

• Stub

• Test Double

• Service Stub

• Design Patterns — the complete patterns catalog.

Pros and Cons

Common Mistakes

1. **Over-engineering: Applying Fake where a simpler solution suffices, adding unnecessary complexity.

2. **Wrong granularity: Implementing Fake at the wrong level of abstraction.

3. **Thread Safety ignored: Using Fake in concurrent context without proper synchronization.

4. **Tight coupling: Violating the pattern intent by creating hidden dependencies.

5. **Premature optimization: Introducing Fake before there is evidence it is needed.

Practice Questions

1. What problem does the Fake pattern solve? Describe a real-world scenario where using it improves code quality.

2. How does Fake differ from alternative approaches? What are the trade-offs?

3. What testing Strategy would you use for code that implements Fake?

4. How would you refactor legacy code to introduce Fake?

5. When should you NOT use Fake? Describe scenarios where it adds unnecessary complexity.

Challenge

Implement a complete Fake example in Python with unit tests. Include error handling, edge cases (empty data, null values, concurrent access), and a performance comparison against a simpler alternative. Document your design decisions.

Real-World Task

Find a section of code in your current project that could benefit from the Fake pattern. Refactor it, write tests, and measure the improvement in testability, coupling, and cohesion.

Security Tip: When implementing Fake, ensure proper input validation, avoid exposing internal state, and follow Least Privilege. At DodaTech, all implementations undergo security review.

Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro.