Now, when working on BTGT I have changed job (oh yeah!) and suddenly I started using JUnit much more than previously. I have also noticed how this project is coming back to life (see the recent discussions on JUnit lists). And I thought like "hey, why shouldn't I rewrite the Practical Unit Testing this time with JUnit instead of TestNG?". At first I rejected the idea. I'm still a TestNG guy and I like it more than JUnit. But then I thought about it some more and it occurred to me that:

there are many JUnit users who might not want to buy the book because of the "TestNG" written on the first page,

the main topic of the book is writing of good unit tests, and NOT a particular technology.

This means that by rewriting code samples and changing few sections related to TestNG-specific features (i.e. replacing them with JUnit counterparts) I can prepare a new book that can be read by much wider audience (TestNG is still much less popular than JUnit).

The status today is that the JUnit version of the Practical Unit Testing book is nearly finished. There are still some technical things that should be done (i.e. proofreading) but the content is already there. After this new-old ;) book is published I go back to "Bad Tests, Good Tests" (still looking for examples of bad tests!).