I’ve spent almost a year writing and editing Unit Testing Principles, Practices, and Patterns. It was a lengthy, but fun and fulfilling undertaking.

I’ve published the book with Manning (one of the most prominent publishers in software development). The biggest benefit of writing a book with such a publisher (as opposed to releasing it on your own) is the strict and rigorous review process.

The book has gone through multiple review stages. One of those stages is when Manning asks people from the industry (not Manning employees) to review the book and leave very detailed feedback with all the "goods" and "bads" they find in the book. The reviewers also get to rate the book.

Guess what book broke the record for the highest-rated book at Manning?

You guessed it, it was this book about Unit Testing.

My editor (who was also the book manager) said the book received the highest rating among all books she managed at Manning.

To be honest, I did expected that people would like the book but didn’t anticipate so overwhelmingly positive feedback.

Here are some of the quotes from reviewers (emphasis mine):

This is a book that every developer and software architect should read. You’ll probably find yourself reading it again and again and getting more out of it each time. This book will feed into your professional practice and make you a better developer. Writing better unit tests forces you to become a better software architect. This book is an indispensable resource.

Absolutely practical and useful book. The author can convey his ideas in a consistent and pragmatic way, with all the necessary underlying theory and without architecture astronaut’s solutions.

I finally formulated for myself how and when should I use mocks. Incredibly good thought about testing a unit of behavior, not a unit of code.

It’s simply brilliant.

This is the kind of book that makes you feel more confident about unit testing. It gives you a framework for discussing tests using objective measures. This book should be read by all developers.

The writing is very good. Sentences are concise and well structured. There is a structural use of repetition to help you remember core points. I am very impressed.

This book provides the type of content that you have to read between the lines of many other books. It puts into words things that are often intuited. The concept is very interesting and the audience is well matched to the content.

This book will not only help you write better tests but more importantly will help you write code that is more easily testable. I wish I had this book twenty years ago when I was starting my careen in software development

Finally a book that goes beyond simple tutorials and teaches how to write readable and maintainable tests

Roy Osherove’s book is one of my favorites books about testing. This one is going to be one of my favorite books too. It’s absolutely practical, covers different aspects of real-world programming.

This book covers about any question you could have about unit tests, from what to test about database calls to whether or not you test what you log. In my mind this is a great design book under the guise of a unit testing book. Don’t get me wrong. The author goes to great lengths on unit testing, why you should do it, and how to identify and write good tests. But the real heart of this book is on how to structure your code to unit test effectively. There’s a lot of value in that that a lot of resources don’t explore.

Mind you, these are programmers who:

  • Read the book in full

  • Are not my followers

  • Don’t work at Manning

  • Remained anonymous throughout the whole review process

Here are also a couple of reviews from Amazon and GoodReads:

In any event, highly recommend that you check it out too:

Again, don’t forget about the discount from Manning and the exclusive bonus.

  1. To redeem the discount, go to the Manning book page and use the nwsentr40 code during checkout.

  2. To redeem the exclusive bonus (a free enrollment in my course 5 Non-Obvious Tips for Writing Better Unit Tests), forward your purchase receipt to book@enterprisecraftsmanship.com

This is the last email I’m going to send you about the book, so you should act now if you’re interested in getting the 40% discount and the bonus. All formats are eligible for the bonus. I don’t have control over this discount and the publisher can retract it at any time.

Vladimir Khorikov

P.S. This book is not about making money for me. In fact, I hardly make any money off of the sales at all — about a couple of dollars for each sale, which, if you account for the time I spent writing it, is less than the minimum wage in hourly terms.

I pitch this book because I genuinely believe people will get a great deal of value out of it. If you know someone who might benefit from improving their unit testing skills, please share this book with them.

P.P.S. If you want to consult with me, reply to this email with the word "consult", and we can chat more.