What will be new in JUnitDoclet 2.0?

First of all, we want to keep everything as close as possible to release 1.0.2.

The template mechanism will change from one file for all templates to one file per template. We want to get rid of the line numbers and indentation problems this way. A converter will be provided.

The core of JUnitDoclet will be freed from all dependencies to the JavaDoc API. It is the first step in preparation of plugins for modern IDEs. Of course, there still will be a doclet frontend to the core.

The new release will be able to generate abstract TestCases for interfaces and abstract classes. Those tests will be applied to all instanciable classes implementing the interfaces / deriving from these abstract classes.

How about reusing test cases? Liskov Substitution Principle says, a class B derived from class A should behave as class A, too. Applying the tests from ATest on B would verify that. Because these additional test cases can be generated without manual interference, one will get even more out of exisiting test cases.

Some users of JUnitDoclet complained, that one test method per application method sometimes is not enough. We will provide a way to handle those rare situations in a convenient way.