JUnitDoclet is helping you with the repeating tasks of writing JUnit tests.
Basically JUnitDoclet is generating and maintaining TestCases and TestSuites based on your application source. And it is helping to keep these tests in sync during development, especially after refactoring (renaming, moving, ...)!
No tests get lost!
You'll notice that you don't get interrupted by "trying to remember the syntax of a test case" when you are working with it for a while. Because is much less work (or pain ?) to write a test, you'll see yourself writing more tests. That tends to be a good thing.
For public accessor methods (like getValue/setValue or setFlag/isFlag), a combined default test is generated based on the type accessed. Of course you can modify that test and your modifications will remain when re-generating.
Using JUnitDoclet, you stay in control. The generated code is based on templates, just adapt them if necessary.
There is no need to outsmart JUnitDoclet. This tool is standing at your side, not in your way. This means: It does not do it all, it's "just" helping as much as it can. You decide everything else.
For details please see:
http://www.intellij.org/twiki/bin/view/Main/JUnitDoclet (which points you to) http://www.junitdoclet.org/
Working as a Doclet all it needs is JavaDoc, maybe as an ANT target. This way it is working with IDEA 2.x as well. But we think about making it a IDEA-Plugin too. Please send any suggestions about the plugin idea to firstname.lastname@example.org .
BTW: We developed JUnitDoclet using IDEA 2.6 and the EAP versions. Great tool, getting even better!