The basis of this book seems to boil down to using basic applications, overly explaining each line and then making reference to another book with more information. The time spent reading and understanding some author's example project would be better spent reading the books that this book quotes.

Chapter wise, chapter 2 could have been left out completely; just as the book broke past the intro phase and getting onto the good stuff it jumped straight into endless code and nunit tests code, it's needed to complete the book, as it breaks down nunit tests and shows practical explains, but I'd suspect anyone reading it would have skipped that chapter completely.

Chapter 3 feels like another re-write, it's based all on "Refactoring", and pretty much tries to condense a full on book (Refactoring by Martin Fowler), into a few pages. So far, the book very much spoon feeds you information, but it also comes across like it's just trying to fill up space rather than promoting and educating Test-Driven Development.

Chapter 5 picks up the same a bit, it's still in the introductory stages, explaining the overall "media" project; This chapter does nicely use a Gateway Design Pattern, to implement object retrieval from the database, though I wouldn't agree on the implementation fully. It gets the point across though; but I still think, within the first couple of pages of the book, if they showed a nice, colour-code class and nunit fixture's, with accompanying explanations, this would have achieved in a short period of time, the points the author's are trying to get across.

Chapter 6, goes through using a DTO, Data Transfer Object, as explained in PoEAA. This book is beginning to be more about proper code organisation and patterns, then Test-Driven development. But the underlying theme always comes back to doing Nunit tests.

Chapter 7 focuses on Customer Test cases by using FIT
http://fit.c2.com

I wasn't able to finish reading this book cover-to-cover, flicking through the rest of the book, it seemed very much, wash-lather-rinse and repeat type book. It kept building on the fake project from previous chapters, implementing more coding and spoon feeding you code.

On a final ditching effort, I've decided to read the books, that this book quotes and thought that would be a better use of my time.