Menu
▾
▴
#234 Cancel button when running JUnit tests
It would be nice if we had a cancel button when running
the JUnit tests. They already are running under the
Slave JVM; if we had a second slave JVM for JUnit, and
added a cancel button, we could reset that JVM, killing
the JUnit tests.
Just a feature request I've had since we gained the
ability to test all - it would be nice to be able to
break our, or at least, have an option to stop running
tests after a test fails, so that if an early test
fails you don't have to sit there and wait for all the
other tests to finish before you can analyze what failed.
Logged In: YES
user_id=429731
The "Reset" button will accomplish this right now, killing
the Interpreter JVM in which the tests are running.
Granted, that might destroy some unreleated context you've
built up, and it's also not obvious that the button affects
the tests-- that's perhaps a UI/presentation issue.
The problem with adding another slave JVM is that you won't
be able to set a breakpoint in your tests to debug them
(which can be quite handy).
Logged In: YES
user_id=1039473
I forgot about debugging test cases. At any rate, currently
the hour glass comes on when you begin testing, which
prevents you from clicking the reset button.
Logged In: YES
user_id=430590
I am skeptical of any feature that requires running yet
another JVM.
I like the idea of making it possible to kill the slave JVM
in the middle of
unit testing as long as the user understands that it will
terminate the current interactions session and the
associated debugging capabilities. Perhaps a dialog box
requiring confirmation is the right way to handle this issue.
Logged In: YES
user_id=697810
I really like the idea of a cancel button, but as has been
said, yet another JVM is not a good idea, I think. The
trick is to preserve the test case errors that have already
been generated, which will be lost if a reset is performed
during testing, leaving only the cryptic result that
"Previous test was interrupted."