You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Dy...@Sun.COM on 2007/11/01 21:15:38 UTC

Re: Testing of derby.log

Vemund Ostgaard <Ve...@Sun.COM> writes:

> I'm looking at converting some old tests for derby.log to JUnit.
>
> The nature of these tests mean that derby.log will be deleted by the
> tests, and I will have to shut down the engine to be able to test the
> effect of changes to properties.
>
> Does this mean that these tests should not be a part of one of the
> regular suites in suites.All, but rather be run in it's own jvm to
> avoid deleting history from other tests and rebooting the Derby
> engine?
>
> Any advice on how to best handle this?

I think Julio asked about the same thing a while back, and he got some
suggestions from Knut. I don't have the reference now but I'm sure
you'll find it with nabble...

-- 
dt