hehe... - Focused on real-life examples (not the "money" type example). It does not shy from hard cases. - The book takes you through end to end cases. It does not just show you how to write test case, but also how to organize your projects, how to run your tests in different environments, how to automate them, etc. - Lots of examples from the J2EE world. It covers all J2EE components. - Addresses testing automation through the full project lifecycle - Covers some "new" frameworks/versions: Maven, DynaMock, Cactus 1.5, etc. - Easy to read style (according to reviewers), but this is a subjective criteria... It does not cover: - GUI unit testing - Multithreading testing - It's not a book on the theory of unit testing. It's a practical book sprinkled with best practices advice. The main reason is: - I'm not an expert in these domains and I prefer not to talk about things I haven't experienced first hand in real life projects. BTW, I'm currently working on a big project where we do Swing unit testing, so the second edition might include some GUI testing... - Lack of time Hope it helps, -Vincent