Python Know When Mocking Makes a Test Less Useful

Mocks work best at external boundaries.

Understanding the Concept

Mocks work best at external boundaries. Excessive mocking ties tests to implementation details and can make incorrect code look correct because every collaborator returns exactly what the test expects.

Fakes and integration tests help verify behavior that a simple call-count assertion may miss.

How this fits into a real test suite

A reliable test starts with a specific expected behavior. Keep the fixture small, arrange the input, call the real code, and assert a result the reader can verify. Add one boundary or failure case so the test does not pass only for a convenient example. In a larger project, run the same test automatically after each change.

Tests are repeatable experiments. Use temporary resources and injected dependencies where possible; when the environment is part of the requirement, add a separate integration test rather than weakening the unit test.

Worked Example

Read the code from the first line to the last. Identify which values are inputs, which operation is being demonstrated and what should happen before running it.

def percentage(part, whole):
    if whole == 0:
        raise ValueError("whole must not be zero")
    return part / whole * 100

assert percentage(25, 100) == 25
print("Real arithmetic tested without mocks")

Walkthrough: What Each Part Does

• The definition percentage creates reusable behavior. Its body runs when called, awaited or instantiated; defining it alone does not run the body of an ordinary function.
• The final check compares actual behavior with an explicit expectation. A successful test tells you that this particular case passed, not that every possible input works.

This demonstration focuses on one practical behavior. Before changing several lines, vary one input or one configuration choice and check whether the result changes for the reason you expected.

Example Output

Real arithmetic tested without mocks

The output above was captured by running the example in the available Python environment. The order of concurrent events, durations and platform-dependent values can legitimately differ on your computer.

Important Behavior and Edge Cases

Mocking a pure arithmetic helper instead of exercising its actual logic.

Fakes and integration tests help verify behavior that a simple call-count assertion may miss.

Practice Exercise

Identify which dependency of a payment function must be faked and which calculations should remain real.

Write down the result you expect before running your changed code. Check at least one normal case and one boundary or failure case. If your example starts workers or opens resources, verify how they are cleaned up.

Further reading: official documentation and API reference.

Common Beginner Mistakes

• Mocking a pure arithmetic helper instead of exercising its actual logic.
• Writing assertions that check implementation details but fail to validate the behavior that matters to the caller.

Key Takeaways

• Mocks work best at external boundaries.
• Fakes and integration tests help verify behavior that a simple call-count assertion may miss.
• Practice: Identify which dependency of a payment function must be faked and which calculations should remain real.