Thanks Knut. This would work for me. However, I think it my be good to
store the derby.log in TestConfiguration.getCurrent().getFailureFolder()
directory in case of a test failure on tearDown. This would solve also
DERBY-2614.
Just for now I do not know how to get the test result in tearDown
function. Still exploring the possibilities. I try to find the source of
junit 3.8. Can somebody point me to a place where I can find them? They
are not at junit.org nor the sourceforge.net. There are only newer versions.
Any other idea?
Thanks
Julo
Knut Anders Hatlen wrote:
Julius Stroffek <[EMAIL PROTECTED]> writes:
Hi,
I noticed that the derby.log is not kept in any place for the failed
test during a suite run. Am I doing something wrong? Is it possible to
setup a test in a way that it will keep the derby.log file? Of course,
there is derby.log in derby.system.home directory but it got
overwritten couple of time during the suites.All run.
I don't think you're doing anything wrong. It's just that derby.log is
overwritten each time the engine is rebooted. Perhaps running the tests
with derby.infolog.append=true would help? But I guess derby.log would
still be overwritten by the network tests that spawn a new process.
It makes a sense to me to keep the log file especially in cases when
you are exploring problem that just happens occasionally.
I agree, that could be really useful in some situations.
One hack that could help you if you have GNU tail installed (called tail
on GNU systems and gtail on other systems), is to have this command
running in another terminal window:
$ gtail -F derby.log > full-derby.log
With the -F option, tail detects whether the file has been deleted or
truncated and continues reading from the tail of the new file, so you'll
find most of what's been written to derby.log in full-derby.log.
