July 2013
Intermediate to advanced
370 pages
8h 27m
English
Unit testing is not something I provide as abstract advice. I have used automated unit tests for all the code in this book because I’m working with an evolving language. Groovy features change, its implementations change, bugs are being fixed, new features are added, and so on. I updated my installation of Groovy on my machines quite a few times as I was writing these chapters and code examples. If an update broke an example because of a feature or implementation change, I needed to know that quickly without expending too much effort. Furthermore, I refactored several examples in this book as the writing process progressed. The automated unit tests helped me sleep better at night because I knew ...
Read now
Unlock full access