Chapter 1. The Practice of Test Automation
Test automation is a practice that will make you think differently about coding. A typical non-tester approaches a problem by squabbling about some code in the editor and changing it until it works. Like working with clay, you start from a lump and carefully craft it into a bowl, and once satisfied, let it dry. Once it has dried, there is no way you can change it.
When you start doing test automation, you will quickly identify the key issues with how you've been writing code before:
- You start writing code on a blank sheet without any clear intent on the result
- You don't know when it's time to stop writing code
- You don't know whether your code will keep on working when you add more code
Test automation comes to grips with these issues and provides a process for writing code in a more structured and organized fashion. You start out with a clear intent, implement the code until your tests are green, and refactor it until you're happy with the end result.
Functional programming will open your mind to the flaws in the code you've written previously. You will find that the number of programming errors are reduced when your code becomes stateless. Complexity is reduced by removing the deep object dependency graph from your application. The intent gets clearer when all it consists of is functions and data, where functions operate on data.
Together, test automation and functional programming is a harmonious match that brings together good coding practice with good code, making you, the programmer, fall into the pit of success. By reading this book, you will understand how to combine the two and become a better programmer.
In this chapter, we will cover the following topics:
- What is testing
- The purpose of testing
- Testing with intent
- Writing regression tests
