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.

One of the fundamental books in unit testing. Get it!

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.

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.

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.

Good content. Provides a good framework on unit testing, integration testing and refactoring. Also touches on system architecture a bit, in terms of testing. Examples are few but to the point. Recommend it to mid to senior developers that is seeking to form a formal basis on unit testing

Excellent Book on Unit testing pcrinciples. But be aware that you Need already be comfortable with the technical Side of testing.

Other than that the Book very clearly explains how to Write Good Unit tests that will help you have a refactoring Safety net for your application.

This is done by elaborating on the 4 pillars of good tests and the difference between different unit test schools and styles.

To sum it up it is an excellent read and I learnt a lot, I have not been aware of before even though I practiced TDD and testing in general. So buy it if you want to write better tests is my advice.

One of the best books I've ever read, excellent content

Después de leerlo, puedo decir que es de mis libros que de encuentran en mi top 5 en materia de desarrollo de software.

Explains very well why unit tests are important and goes into detail about different ways of writing them, as well as good practices and things to avoid. Was able to apply to my work