Skip to content

Object Mother Pattern — Test Data Factory

DodaTech Updated 2026-06-29 3 min read

In this tutorial, you'll learn how the Object Mother pattern centralizes test data creation in factory classes to reduce duplication.

What You'll Learn

how the Object Mother pattern centralizes test data creation in factory classes to reduce duplication.

Why It Matters

Creating test objects in every test duplicates setup code. Object Mother provides reusable test data.

Real-World Use

Test data factories in factory_boy (Python), FactoryBot (Ruby), and Mother objects across languages.

The Object Mother Pattern

The Object Mother 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 --> ObjectMother
    ObjectMother -->|stub| Service
    ObjectMother -->|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 ObjectMother
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 Object Mother.
  • Object Mother: 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.
  • Test Data Builder

  • Mock

  • Test Double

  • Design Patterns — the complete patterns catalog.

Pros and Cons

Pros Cons
Provides a clean, reusable solution to a common problem Can introduce unnecessary complexity for simple problems
Improves code maintainability and readability May reduce performance due to additional abstraction layers
Establishes a shared vocabulary for developers Requires team familiarity with the pattern
Reduces development time through proven solutions Overuse can lead to overly abstract, hard-to-follow code

Common Mistakes

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

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

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

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

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

Practice Questions

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

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

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

  4. How would you refactor legacy code to introduce Object Mother?

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

Challenge

Implement a complete Object Mother 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 Object Mother pattern. Refactor it, write tests, and measure the improvement in testability, coupling, and cohesion.

Security Tip: When implementing Object Mother, 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.

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro