This books describes techniques to build a scaffolding of automated tests. They cover string verification, exceptions, testing race conditions, etc. While those are very technical, I sense some wisdom as a watermark to exploit all "seams" (as in Working Effectively with Legacy Code) and to decouple tests from code. I gave this book only three stars so far, but it deserves another read and some more hours behind the keyboard ...
To t is very clear that the author is quite knowledgeable and is constantly searching for information that will further his knowledge. However, this book also demonstrates well one of my general problems with technical manuals/textbooks of the IT industry: making the real message hard to understand by over naming or the use of acronyms. Far too much of the examples could be made so much easier to understand if there wasn't all the names and acronyms given. Cut to the chase and just give us the real info!
My biggest problem with this book though is that the author points out that most people understand the coding principles to be able to develop with a test driven mindset, they just need to understand the concept behind test driven development before they will actually do it. While I agree with his assessment, it is extremely frustrating to have the real problem be so succinctly stated and then immediately ignored in favor of what I'm sure the book publishers think will appeal more to their intended audience.
Please publishers, do give us what you think we want to hear/read/see. Give us what we really need, what the taglines promise!
This book was appropriately named but poorly taglined. I think that I would better be able to understand the code or even be able intuit the code if I knew the concept of or why of test driven development.