On 6/8/08, Kristian Waagan <[EMAIL PROTECTED]> wrote: > Kathey Marsden wrote: > > I am dealing with a problem where I get a hang in the tests, but several > tests error before the hang. > > I was thinking it would be useful to print the exception trace for failed > tests after printing the test if > > derby.tests.trace=true. Does anyone have objections to such a change? The > traces would still print > > in the summary at the end of the run. > > > > Just as a point of input, have you looked at DERBY-2667? > There's a patch there that might be of interest: > derby-2667-WriteExceptionsToFileAsTheyHappen.diff > > The advantage of the patch over the other approach, is that you'll get the > possibility to look at the stack trace early without having to run the tests > with any special options. > > That said, I see the value of having the text based runner print the name of > the test being started too (typically used to figure out which test is > hanging). > > > regards, > -- > Kristian > > > > > > Thanks > > > > Kathey > > > > > > > > I am wondering if derby.tests.debug=true was intended for this type of investigating? I think derby.tests.trace=true is more 'permanent' and for everyone, less chatty. See BaseTestCase, e.g. println(String)... You'd check for TestConfiguration.getCurrent().isVerbose().
Myrna
