JUnit Recipes: Practical Methods for Programmer Testing

by J.B. Rainsberger, Scott Stirling (Contributor)

When testing becomes a developer's habit good things tend to happen--good productivity, good code, and good job satisfaction. If you want some of that, there's no better way to start your testing habit, nor to continue feeding it, than with"" JUnit Recipes,"" In this book you will find one hundred and thirty-seven solutions to a range of problems, from simple to complex, selected for you by an experienced developer and master tester. Each recipe follows the same organization giving you the problem and its background before discussing your options in solving it.
JUnit - the unit testing framework for Java - is simple to use, but some code can be tricky to test. When you're facing such code you will be glad to have this book. It is a how-to reference full of practical advice on all issues of testing, from how to name your test case classes to how to test complicated J2EE applications. Its valuable advice includes side matters that can have a big payoff, like how to organize your test data or how to manage expensive test resources.
What's
- Getting started with JUnit
- Recipes
servlets
JSPs
EJBs
Database code
much more
- Difficult-to-test designs, and how to fix them
- How testing saves time
- Choose a JUnit
HTMLUnit
XMLUnit
ServletUnit
EasyMock
and more!

Genres: Programming, Technical, Computer Science, Software, Reference

754 pages, Paperback

First published July 15, 2004

Reviews

[Peter Sichevsky]

I think it's a good read. I fonud it practical and easy to understand, even though I'm not a big fan of computer books, I'm more into documentation and technical manuals.

[Ivan Idris]

JUnit is the most popular unit testing framework for Java. JUnit gives you tons of useful unit testing tips. This book is now outdated, since it covers an older version of JUnit – the one without annotations. Still I learned a lot of basic principles from it.

[Jakub Zalas]

It’s true this book is in some parts outdated. It was published in 2004 after all. However, it gives a great insight into practices in the days TDD was gaining popularity (Kent Beck’s book was only published two years earlier).

Yes, some advice is dated, but a lot still holds. Some of it is unfortunately forgotten by a modern developer.

[Daniel Koller]

great book, lots of programmer testing wisdom.
Of course, the jUnit aspects are obsolete after so many years.

[Christophe Addinquy]

Ma note de lecture complète en français ici