In this chapter, we saw how we can write acceptance tests that can be shared with other stakeholders to review the behavior of the software and not just be used by developers as a way to verify that behavior. We saw that it's possible to express the specifications of the software itself in the form of scenarios and examples, which guarantees that our specifications are always in sync with what the software actually does and that our software must always match the specifications as they become the tests themselves.
Now that we know how to move a project forward in a test-driven way using PyTest, in the next chapter we are going to see more essential PyTest plugins that can help us during our daily development practice.
