In this chapter, we saw how Tox can take care of all the setup necessary to run our tests for us and how it can do that on multiple target environments so that all we have to do to run tests is just to invoke Tox itself.
This is a more convenient, but also robust, way to manage our test suite. The primary benefit is that anyone else willing to contribute to our project won't have to learn how to set up our projects and how to run tests. If our colleagues or project contributors are familiar with Tox, seeing that our project includes a tox.ini file tells them all that they will need to know—that they just have to invoke the tox command to run tests.
Now that we have seen the base plugins and tools to manage and run our test suite, in the next chapter, we can move on to some more advanced topics that involve how to test our documentation itself and how to use property-based testing to catch bugs in our code.