Community
Participate
Working Groups
3.1 I get frustared over this often. You run your tests, they take a long while each, after a bunch you decide to stop the execution. You press the 'Stop JUnit test run' wanting to halt the execution immediately. And it doesn't! Then you must go to the Debug view (why that name? i'm not debugging, i'm running) and 'Terminate' it from there. That does it.
not a *huge* deal, of course. An annoyance nonetheless. :)
Still present in 3.2 (Callisto). BTW: You don't have to go to Debug view/perspective, the console view can terminate it too.
*** Bug 249570 has been marked as a duplicate of this bug. ***
Re: comment 3 Problem in bug 249570 is that the red button is not even enabled early on. I agree though that both issues should be addressed together.
The reason why the Debug/Console terminate is faster is because this kills the process while the JUnit view stops running the tests and then safely returns i.e. the the workbench for example isn't killed but correctly exited. Therefore the button is also only enabled once testing has started.
*** Bug 303559 has been marked as a duplicate of this bug. ***
A fix for this would have to implement this: - enable the stop button earlier - when the test run session has already started, try the JUnit way to stop (the existing request for a clean stop that e.g. allows tearDowns of tests and TestSetups to clean up) - when the stop button is pressed while the test run session has not yet started, or when it is pressed a second time, ask the user whether he wants to terminate the process (default button: Yes)
I found a related problem: When I'm debugging a unit test, and, after hitting a breakpoint, I decide to terminate the test in the debug view, the red 'stop' button in the junit pane stays enabled. I think the current behaviour of the junit stop button is a bit confusing. How about letting it behave like the other stop buttons do, so just let it terminate the proces? Or otherwise maybe add a second button 'kill proces'?
Pity that this bug is still present in 4.3.1 (Kepler).
And is still present in Luna too.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Still present in Eclipse 2022-03
