|Print List Price:||$14.99|
Save $12.00 (80%)
Working Effectively with Unit Tests Kindle Edition
|New from||Used from|
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.
- Publication Date : December 8, 2014
- File Size : 570 KB
- Word Wise : Not Enabled
- Print Length : 354 pages
- Text-to-Speech : Enabled
- Language: : English
- ASIN : B00QS2HXUO
- Screen Reader : Supported
- X-Ray : Not Enabled
- Enhanced Typesetting : Enabled
- Lending : Enabled
- Best Sellers Rank: #739,181 in Kindle Store (See Top 100 in Kindle Store)
- Customer Reviews:
Top reviews from the United States
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.
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.
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.
* The evolution of a hairy test to something really clean is elegant.
* It skips the usual slow history and get straight to the point.
* I wish more people wrote tests like this. I see so many unit tests that make me sad due to over complicated abstractions that hamper readability. Having a book to point people at will really help.
* Doesn't get carried away with frameworks, DSLs and such, but mostly it's just really straight forward programming.
Thank you Mr Fields! I will be recommending this book to many people.
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.
Top reviews from other countries
The book doesn't really have a "point", it's a collection of principles and ideas. I've tried reading through it linearly, but there's not really a narrative or process to follow, and reading consecutive pages of code isn't fun. I've tried using it as a reference, but it's really not put together in that way.
It feels like there are maybe 50-100 pages of good content, and 200+ filler / repeated source code / waffle.
It is very example centric and the examples evolve during the chapters.
I think it's one of those books that makes you a different (I would definitely say better) as soon as you get to chapter 2.
I would definitely recommend this book to anyone who's hands on (junior or senior) in the field.