Unit Testing Principles, Practices, and Patterns: Effective testing styles, patterns, and reliable automation for unit testing, mocking, and integration testing with examples in C#

One of the most helpful resources I found when it comes to test effectively, beyond the "The more test the better" rule of thumb the main take away from this book is "You either create solid tests that brings value to your software or you wrote none" The approach of how to calculate the value of a tests is quite accurate. Test quality that can be measure is something really valuable.

I have been doing unit and integration testing for about fifteen years, and I have read many books about testing using different languages. This book so far is the best. Most of the books gave simple examples like calculators or dependency injection. This book covered where and how to use each and design your code to be testable. That is very important since testable code requires a different structure or architecture. This book also covers dealing with mock, databases, external services. I think that there is so much information in this book that reading it once might not be enough, and I'm going to read it a second time and use it as a reference when I'm designing and writing my code to make writing unit tests better.

awesome:* amazing breakdown of the two schools of thought with unit testing (haven't seen this articulated well before)* succinct definition for pillars of unit testing, in the past I've seen descriptors -- like in Growing Object-Oriented Software Guided by Tests -- but this is a good categorization of what makes a good unit test* tackles some very relevant approaches to building services and how it impacts your unit testing strategies, layered architecture, domain-driven design, functional programming* novel and good name of "observable behavior" as what you want to testto improve:* the name of the pillar "resistance to refactoring" is not intuitive* while I personally agree with the pillar "resistance to refactoring" being very important, the argument and in-practice definition could be fleshed out quite a bit more. Part of the grey area, for me, is "observable behavior" not being defined better in practice. For example, I haven't been able to figure out when to stub vs when to verify for repository reads in my application services. It's not clear from the book or from its definition of "observable behavior", how to make your unit test resistant to refactoring.

Unit tests are a necessary for complex software applications, but there are very few guidelines and resources on how and what exactly should be unit tested. This book takes unit testing at the next level. I completely agree with the author, we should unit test a unit of behavior and not a unit of code. I highly recommend this book for all software developers.

Bob is young and just started writing unit tests because he has heard it's such a great idea, he picked the "art of unit testing" book from bookshelf and he is ready to go, writes many tests, he is more than happy, finally, something checks his job, he is not afraid anymore to bug fix code because something is checking if he is not introducing any new bugs. Then, this day comes, Bob wants to rearrange his classes, methods and suddenly he is in a situation when he has to fix a million tests. Don't be like Bob, do a favor to yourself and buy this book.

This book is amazing! As usual Vladimir is super clear snd pragmatic. This is not only about unit testing, but architecture as well. I personally loved it!!!!

This book contains many great advices and examples about different aspects of unit testing. Very helpful for me.

Great book, explains various theoratical concepts around unit tests. I'm keeping this as my reference, or source to make software training about unit testing.