At the beginning of this book, I spoke about dogma and how this book is a written form of my dogma. It details how I prefer to write applications and summarizes everything I've learnt about test-driven development up until this point in time.
There have been a number of recurring themes that many chapters have touched on across the book: the notion of 'strict' test-driven development, how and when to 'cheat', systematic refactoring, and so on.
Some dev teams like to adopt the mantra of move fast and break things. TDD is the opposite—we must go slow and think about things. To understand what this means in practice, we can compare TDD with various other popular testing techniques.
The following topics will be covered in this chapter:
- Test-driven development as a testing technique
- Manual testing
- Automated...
