After reading this chapter, you will hopefully no longer think of automated checks as regression tests; instead you should think of them as living documentation that continues to grow and flourish as the code they are validating changes. When things go wrong you will be able to take screenshots to aid diagnosis, as well as being able to fluently read stack traces. You will know how to connect your tests to a Selenium-Grid to provide additional flexibility. Finally, you will also have a good understanding of why reliability matters and how this feeds into successful continuous integration, continuous delivery, and continuous deployment.

In the next chapter, we are going to have a look at exceptions generated by Selenium. We will work through various exceptions that you may see and what they mean.