On Mon, 2006-06-26 at 12:40 -0400, Thomas Fitzsimmons wrote:
Mark Wielaard wrote:
They make it possible to use
RunnerProcess just as you could use SimpleTestHarness (e.g. echo
gnu.testlet.some.test | runtime RunnerProcess) by just returning when
stdin is empty (and in.readLine() returns null).
This can already be done using the current Harness:
jamvm Harness gnu.testlet.some.test
Harness also supports specifying multiple tests:
jamvm Harness gnu/testlet/java/awt/Frame/size1.java
gnu/testlet/javax/swing/JTable/addColumn.java
I know, but that is a terrible way for debugging. Hunting down a crasher
bug for example is really, really awkward using the Harness since it
does way too many things. When examining tests (especially under gdb)
for debugging you need to be able to run them just through the
RunnerProcess to make sure you are looking at just the thing that fails.
It works nicely with that one-liner patch though, so it isn't really
another way to run tests, it is just to make sure you can run the tests
by hand as if the Harness would run them.