Build a Practical Dependencies and Test Doubles Example in Software Testing Fundamentals

Define the build target

For Dependencies and Test Doubles, test a component with one controlled dependency, then remove a flaky source such as real time, network, or shared mutable state and confirm the test stays deterministic. Build the boundary case using this implementation lens: Use explicit behavior contracts, test cases, fixtures, doubles, integration boundaries, failure messages, reliability signals, and delivery feedback loops.

Keep the Dependencies and Test Doubles build centered on these technical constraints: Test double purpose and boundary. Deterministic time/randomness/data. Apply them through this path lens: Use explicit behavior contracts, test cases, fixtures, doubles, integration boundaries, failure messages, reliability signals, and delivery feedback loops. Use explicit behavior contracts, test cases, fixtures, doubles, integration boundaries, failure messages, reliability signals, and delivery feedback loops.

Implement the core behavior

Implement Dependencies and Test Doubles around the module artifact—a working dependencies and test doubles exercise with a documented technical result—and keep the implementation specific to this path context: Use explicit behavior contracts, test cases, fixtures, doubles, integration boundaries, failure messages, reliability signals, and delivery feedback loops.

def total_with_tax(subtotal, rate):
    if subtotal < 0:
        raise ValueError('subtotal must be non-negative')
    return round(subtotal * (1 + rate), 2)


def test_total_with_tax():
    assert total_with_tax(100, 0.08) == 108.00


def test_negative_subtotal_is_rejected():
    import pytest
    with pytest.raises(ValueError):
        total_with_tax(-1, 0.08)

pytest -q

The success case passes and the invalid input is rejected by an explicit test.

practice/\n├── README.md\n├── dependencies-and-test-doubles-build.py\n└── evidence/\n    └── expected-result.txt

Run the complete path

Run one realistic Dependencies and Test Doubles case end to end and record the required evidence: the module-specific command, output, test, rendered state, query result, log, or measurement that proves the exercise worked. Interpret the result through this path context: Use explicit behavior contracts, test cases, fixtures, doubles, integration boundaries, failure messages, reliability signals, and delivery feedback loops.

Change one meaningful condition

Modify one condition central to Dependencies and Test Doubles using this path context: Use explicit behavior contracts, test cases, fixtures, doubles, integration boundaries, failure messages, reliability signals, and delivery feedback loops. Predict the new result before rerunning the same workflow.

Verify the artifact

Your deliverable is a working dependencies and test doubles exercise with a documented technical result.

Common mistakes to avoid

• Mocking the unit under test.
• Overspecified call-order assertions.
• Real external network in unit test.
• Shared test data leaks between cases.