- Paperback: 352 pages
- Publisher: CreateSpace Independent Publishing Platform (December 9, 2014)
- Language: English
- ISBN-10: 1503242706
- ISBN-13: 978-1503242708
- Product Dimensions: 6 x 0.8 x 9 inches
- Shipping Weight: 1.3 pounds (View shipping rates and policies)
- Average Customer Review: 10 customer reviews
- Amazon Best Sellers Rank: #747,250 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Working Effectively with Unit Tests Paperback – December 9, 2014
|New from||Used from|
Frequently bought together
Customers who bought this item also bought
If you buy a new print edition of this book (or purchased one in the past), you can buy the Kindle Edition for FREE. Print edition purchase must be sold by Amazon. Learn more.
For thousands of qualifying books, your past, present, and future print-edition purchases now lets you buy the Kindle edition for $2.99 or less. (Textbooks available for $9.99 or less.)
Try the Kindle edition and experience these great reading features:
Showing 1-8 of 10 reviews
There was a problem filtering reviews right now. Please try again later.
Would reccomend picking this up in the Kindle format as some of the code formatting in the physical copy can be a bit hard to read.
As with the maturity of fast-paced testing community, most of the observations in the book are opinions. As @JayJay Fields himself says "You won’t write better software by blindly following advice." So, consider the opinions/answers and use them as they best suit your needs.
While I agree with most of the observations/practices in the book, my only quip with the book was "do the examples overuse builders and mocks?" I often write unit tests that exercise external dependencies as this tells me when my code breaks due to a change in external dependencies. This may be the reason for my quip. That said, I haven't thought about how to convey the same information without builders/mocks.
I don't disagree with much of this book, it's just that it doesn't contribute much new to the world of unit testing, in my mind.
Why do you write tests? What do you try to get out of testing? How do you make failing tests useful? By the time you finish this book you should have a been driven to think about those questions and more. Even it you don't agree with Jay's approach this book will make you think.
You should read this book.
I have recommended this book to colleagues at Atlassian and Canva, both well-recognized software development shops, because everyone needs to continue working effectively with unit tests. The book also is great foundation for those developers who want to become excellent in all aspects of quality assurance and delivering business value efficiently.
As for the review that expressed that there is nothing new or that the examples are convolutedly bad, perhaps writer of that review would be so kind as to invite everyone to come and work with him on the .NET unicorn and rainbow middleware project that is so magnificent it has perpetually excellent tests and code.
As Michael Feathers mentions in the preface: "Reading it, you’ll learn a lot about unit testing. But, more than that, if you read between the lines you’ll learn a lot about how to see and think about software".