Python Fake Time and Randomness in Automated Tests

Randomness and time are dependencies just like a database connection.

Understanding the Concept

Randomness and time are dependencies just like a database connection. Make them injectable to test calculations deterministically without changing the behavior users see in production.

Avoid asserting one undocumented sequence across different algorithms or random implementations.

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.

import random

def roll_die(generator):
    return generator.randint(1, 6)

first = random.Random(19)
second = random.Random(19)
results_a = [roll_die(first) for _ in range(4)]
results_b = [roll_die(second) for _ in range(4)]
print(results_a == results_b)

Walkthrough: What Each Part Does

The imports make random available. These are standard-library building blocks unless the example explicitly names an external tool.
The definition roll_die 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

True

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

Using a fixed pseudorandom seed for security tokens rather than only for repeatable tests.

Avoid asserting one undocumented sequence across different algorithms or random implementations.

Practice Exercise

Inject a fake random object whose randint method returns six, and assert the caller receives six.

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

Using a fixed pseudorandom seed for security tokens rather than only for repeatable tests.
Writing assertions that check implementation details but fail to validate the behavior that matters to the caller.

Key Takeaways

Randomness and time are dependencies just like a database connection.
Avoid asserting one undocumented sequence across different algorithms or random implementations.
Practice: Inject a fake random object whose randint method returns six, and assert the caller receives six.