63 books
—
8 voters
Goodreads helps you keep track of books you want to read.
Start by marking “Working Effectively with Unit Tests” as Want to Read:
Working Effectively with Unit Tests
by
Available at http://wewut.com
Unit Testing has moved from fringe to mainstream, which is great. Unfortunately, developers are creating mountains of unmaintainable tests as a side effect. I've been fighting the maintenance battle pretty aggressively for years, and this book captures the what I believe is the most effective way to test.
This book details my strong opinions on ...more
Unit Testing has moved from fringe to mainstream, which is great. Unfortunately, developers are creating mountains of unmaintainable tests as a side effect. I've been fighting the maintenance battle pretty aggressively for years, and this book captures the what I believe is the most effective way to test.
This book details my strong opinions on ...more
Friend Reviews
To see what your friends thought of this book,
please sign up.
Reader Q&A
To ask other readers questions about
Working Effectively with Unit Tests,
please sign up.
Be the first to ask a question about Working Effectively with Unit Tests
Community Reviews
Showing 1-30
It says "read", but that would be an exaggeration. "Briefly tolerated its existence before setting it on fire" would be more accurate. It burnt remarkably well, 5 stars.
I wish every developer I work with had read this book (including the past me). It distills into a surprisingly short amount of pages many important lessons that I've learned the hard way over a number of years. For a beginning or intermediate unit tester this book is a must-read. The most experienced unit testers may not find much new in it, but even they can benefit from seeing unit testing from the author's unique point of view.
What sets this book apart is its hands-on approach. You're thrown ...more
What sets this book apart is its hands-on approach. You're thrown ...more
A quick, enjoyable read. The focus of the book is how to improve ROI of your unit tests, and provides helpful suggestions to achieve this. There is no dogma here, nor anything revolutionary, but it's a solid addition to the testing literature.
If I have to list a downside, it's that all the examples are Java, and I wonder if some of the patterns are less valuable in other (say dynamic) languages. I would have loved to hear the author's thoughts on this, but it's a minor quibble, and I would still ...more
If I have to list a downside, it's that all the examples are Java, and I wonder if some of the patterns are less valuable in other (say dynamic) languages. I would have loved to hear the author's thoughts on this, but it's a minor quibble, and I would still ...more
This book is a breath of fresh air!
Things I really like:
* 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 programmi ...more
Things I really like:
* 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 programmi ...more
This is a book I plan on strongly recommending to other developers. Jay Fields presents his strategy for testing and his definition of a unit test. The book starts with some marginal unit tests and slowly improves them. I found myself feeling uncomfortable with the initial version of the tests and it was rewarding seeing the tests improve and having that uncomfortable feeling disappear.
Why do you write tests? What do you try to get out of testing? How do you make failing tests useful? By the tim ...more
Why do you write tests? What do you try to get out of testing? How do you make failing tests useful? By the tim ...more
As someone who has done TDD for 10+ years, this book still taught me a few new things and made me reconsider how I like my tests setup. I really like the format of the book - by clearly addressing readers already experienced with testing Jay manages to keep the book short and information dense in a way I wish more technical writers would.
I didn't like the layout of the book. It made it hard to find the meat hidden in the book.
The main problem is that the book is probably 50% printed unit tests.
Personally, I find it unrewarding looking through code in a book.
I'd rather have seen carefully chosen snippets that illustrated the author's points.
The code could've been posted online and referred to allowing readers to utilizes IDE's to parse the code.
The author is also a bit dogmatic saying things should never/always (or at least a ...more
The main problem is that the book is probably 50% printed unit tests.
Personally, I find it unrewarding looking through code in a book.
I'd rather have seen carefully chosen snippets that illustrated the author's points.
The code could've been posted online and referred to allowing readers to utilizes IDE's to parse the code.
The author is also a bit dogmatic saying things should never/always (or at least a ...more
An opinionated masterpiece about how to write maintainable unit tests. This book contains lots of details and well thought-out practices. Highly recommended for those who want to step up their game when it comes to unit tests and TDD.
A very pragmatic discussion of the challenges writing unit tests, and the solutions that the author uses.
not a serious tdd book
the book go too fast over many deep contents, providing little insight. examples are really basic as well. waste of money.
the book go too fast over many deep contents, providing little insight. examples are really basic as well. waste of money.
Good book. I think this book is best start point to know (unit) testing. If you are junior, you will find this book is very useful. Recommend it!
Jay Fields uses in Working Effectively with Unit Tests a different approach than most authors that write about TDD: How does test-driven development creates value? As a measurement to judge the different approaches he uses ROI (return on investment) and explains the different side-effects certain styles of tests have. This (at least for me) new way to look at TDD is refreshing and helps to stay away from code bases that are impossible to change after an endless amount of tests are written that n
...more
Great book. Jay did a great job of providing excellent examples and explanations behind why he is changing those tests. Another great thing about this book, that it's 330 pages but they are all about testing, and no history or other unrelated to testing material.
The book is very pragmatic and short. Pretty nice overviews dos and don'ts of unit testing. With excellent examples to prove the points. But I would recommend to read "Growing object oriented software guided by tests" by N. Price first
Great book, but my only quibble is that using Java for the examples requires much more code for writing tests than in a more dynamic language. I definitely learned a lot about designing unit tests, useful in any language.
Meh. It's good. It's probably directed to people that have been using unit tests for a very long time and use them extensively, which is not my case. It does have good info, it's probably that I don't know enough to get all of this book.
Easy to read and informative.
Amazingly crisp yet insightful.
There are no discussion topics on this book yet.
Be the first to start one »
Goodreads is hiring!
No trivia or quizzes yet. Add some now »
“when writing tests you should prefer DAMP (Descriptive And Maintainable Procedures) to DRY.”
—
1 likes
“Tests do not, or at least should not collaborate; it’s universally accepted that inter-test dependency is an anti-pattern.”
—
1 likes
More quotes…
