Summary

In this chapter, we covered the topic of test stability. We discussed some of the things that make an individual test stable—starting with cultural changes on the team and ending with changing personal behavior, such as testing our own tests before committing them to source control.

We also discussed some of the more technical solutions such as using an existing JavaScript infrastructure to check completion of background AJAX requests and JavaScript animations. We also wrapped some of the common Selenium actions to automatically give them the ability to wait for JavaScript events and take a full-page screenshot of the page when something fails.

Now that we have some measure of stability in our tests, we can start spending more time thinking about the test declaration versus test implementation. In the next chapter, we will be testing the behavior of our application.