This book changed my perception of how important is to write tests. By book definition, legacy code is nothing but a code without a test.
The majority of software companies don’t consider writing test is not useful. So here is a thing about testing. You will see the benefits of the test only when you write it. This book provides tons of technics to bring the class under test.
Some of the favorite chapter’s title is
1. I don’t have much time and I have to change it.
2. I need to change a monster method and I can’t write a test for it.
It was released in 2004. Since then it’s been 15 years a lot of things have changed in the software industry. But the concept in books is still relevant and fresh.