TestDriven Development. Extensive Tutorial I’m writing this book because I’m a TDD enthusiast. I believe TDD is a huge improvement over other software development methodologies I have used to deliver quality software. I believe this is true not only for me, but for many other software developers. Which makes me question, why don’t more people learn and use TDD as their software delivery methodology of choice? In my professional life, I haven’t seen the adoption rate to be big enough to justify the claim that TDD is currently in the mainstream. You already have my respect for deciding to pick up a book, rather than building your understanding of TDD on the foundation of urban legends and your own imagination. I am honored and happy you chose this one, no matter if this is your first book on TDD or one of many you have opened up in your learning endeavors. As much as I really hope you will read this book from cover to cover, I am aware it doesn’t always happen. That makes me want to ask you an important question that may help you determine whether you really want to read on: why do you want to learn TDD? By questioning your motivation, I’m not trying to discourage you from reading this book. Rather, I’d like you to reconsider the goal you want to achieve by reading it. A few years ago, I had an apprentice who wanted to learn TDD. Together we started working on a small project to let him grasp the necessary skills through practice, with me sitting next to him, providing guidance. He showed up three or four times, then he resigned, having “more urgent things to do” and “no time”. Since then, he has not progressed in his understanding or utilization of TDD at all. Even today, I sometimes wonder what was his motivation and why it somehow burned out