Please add a key-binding to repeat the last test (as
in, run JUnit on the file on which it was most recently
run). It would *greatly* speed up the test-modify
program-save-compile-test loop.
Also, at the same time, maybe add an option to have
drjava beep instead of displaying that annoying JUnit
notice every time you accidentally click Test on the
file you just modifed...
Ben
Logged In: YES
user_id=429731
Hi Ben--
I'm reassigning this as a feature request rather than a
bug, but it's definitely something that we'll look at.
We've been thinking about making the Test button search for
the correct test class if it is clicked in a regular class
(eg. user clicks Test while looking at class Foo, DrJava
then finds and opens class FooTest and runs it). That
should cut down on the number of annoying messages. We
should also be able to add a key binding to the Test button
(CTRL+T).
Logged In: YES
user_id=431096
We could add a "Do not show this warning again." checkbox on the warning dialog. Actually, this could be used in several different places within DrJava. If the checkbox is checked, it would save a boolean value within the properties file. We should also add an equivalent checkbox within the Preferences dialog (with a more specific description) so that the warning can be reinstated from the GUI.
This could be implemented as a custom class with a static method which takes in the configuration option along with the standard dialog parameters. That would let us convert our existing dialogs in a straightforward way.
Perhaps this should be a separate feature request. :-)