A unit test checks one small component in isolation; an integration test checks components working together; an end-to-end test follows a complete user workflow.
Understanding the Concept
A unit test checks one small component in isolation; an integration test checks components working together; an end-to-end test follows a complete user workflow. Choose the narrowest layer that can detect the intended failure, then reserve fewer broad tests for the connections between parts.
End-to-end tests are valuable but typically slower and more fragile than local unit tests.
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 subtotal(prices):
return sum(prices)
def receipt(prices):
return f"Total: {subtotal(prices):.2f}"
assert subtotal([3, 4]) == 7
assert receipt([3, 4]) == "Total: 7.00"
print("Both component and composition checks passed")Walkthrough: What Each Part Does
- The definition subtotal, receipt 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
Both component and composition checks passedThe 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
Calling any test that exercises two functions an end-to-end test; it may only be a small integration check.
End-to-end tests are valuable but typically slower and more fragile than local unit tests.
Practice Exercise
List three tests for an online store: a price calculator, its database integration, and a complete checkout workflow.
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
- Calling any test that exercises two functions an end-to-end test; it may only be a small integration check.
- Writing assertions that check implementation details but fail to validate the behavior that matters to the caller.
Key Takeaways
- A unit test checks one small component in isolation; an integration test checks components working together; an end-to-end test follows a complete user workflow.
- End-to-end tests are valuable but typically slower and more fragile than local unit tests.
- Practice: List three tests for an online store: a price calculator, its database integration, and a complete checkout workflow.