Hey Kent (or others who have already read the new book!),
What sort of insight and sage advice can we expect in JUnit Pocket Guide?
JUnit Pocket Guide Full Description JUnit, created by Kent Beck and Erich Gamma, is an open source framework for test-driven development in any Java-based code. JUnit automates unit testing and reduces the effort required to frequently test code while developing it.
While there are lots of bits of documentation all over the place, there isn't a go-to-manual that serves as a quick reference for JUnit. This Pocket Guide meets the need, bringing together all the bits of hard to remember information, syntax, and rules for working with JUnit, as well as delivering the insight and sage advice that can only come from a technology's creator.
Any programmer who has written, or is writing, Java Code will find this book valuable. Specifically it will appeal to programmers and developers of any level that use JUnit to do their unit testing in test-driven development under agile methodologies such as Extreme Programming (XP) [another Beck creation].
The book isn't just about how to use JUnit. It is also a general introduction to developer testing. Here is the table of contents:
Automating Tests Why Test? JUnit�s Goals Fixtures Testing Exceptions JUnit�s Implementation JUnit API Test-First Programming Stubs Other Uses for Tests Story of JUnit Extending JUnit JUnit and Ant Running JUnit Standalone JUnit and IDEs Test Infection
Are the sections about Test-First Programming and Test Infection the highlights of those books/articles? If so, I could see recommending it as shorter reading to some people I know. If not, what is the difference in focus?