In this chapter, we saw how to have tested documentation that can guarantee user guides in sync with our code, and we saw how to make sure that our tests cover limit and corner cases we might not have considered through property-based testing.
Hypothesis can take away from you a lot of the effort of providing all possible values to a parameterized test, thereby making writing effective tests much faster, while doctest can ensure that the examples we write in our user guides remain effective in the long term, detecting whether any of them need to be updated when our code changes.
In the next chapter, we are going to shift our attention to the web development world, where we will see how to test web applications both from the point of view of functional tests and end-to-end tests.