I have started a thread in the tracker
"There should be an easy way to debug a single junit. testcase testXXX
method" and also in the eap forum ("do you ever need to debug (not just
run) a single junit test XXXmethod ?")
but I also noticed other tracker requests (Thomas) about often ending up
with way too many target configurations, and I agree with them.
as you can read in the above tracker thread with Dmitry Peshehonov,
to solve both issues we may end up with :
neither run nor debug should create a saved configuration, but there
should be a 3rd ctx menu entry along besides run/debug (create target)
option for each of the 3 pairs above, that should not also start a process.
when a class is both a TestCase and contains a main() it is not obvious
what should be used to run it.
while we may have all these ways of running it (if a single method is
1 main run
2 main debug
3 junitrunner whole class run
4 junitrunner whole class debug
5 junitrunner selectedmethod run
6 junitrunner selectedmethod debug
I'd be happy if the ctx menu would be thinned down depending on where
the cursor is:
- if the cursor is on a single method, then only the choices 5 and 6
need to be shown
- if the cursor is on main then show 1 and 2
- else show 3 and 4
when a class has just a main or is just a TestCase only options 1,2 and
3,4 respectively may appear in the ctx menu..