db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vemund Ostgaard <Vemund.Ostga...@Sun.COM>
Subject Testing of derby.log
Date Mon, 29 Oct 2007 14:56:57 GMT
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?


View raw message