David Van Couvering wrote: > Well, yes, but one might argue that we're going about it the wrong way: > "It takes too long to run derby tests because it takes so long to start > up the database." "Ok, well, let's fix it so that you don't have to > restart the database for each unit test."
I think for the tests it's really a case of "It takes too long to run derby tests because we run a separate JVM for each test case". My total guess is that making derby boot/create databases faster could bring the tests down from 5+ hours to 4+ hours. My guess for moving to JUnit wil bring them down to under 2 hours. It's all good work, complementing each other. Just when I see someone complain about somthing in open source, my automatic reaction is to get them involved, complaining won't fix anything, "doing" does. Seems like the JUnit work should have the option of either re-using & cleaning the current database, or creating a new one. Might be a useful comparision across a set of tests. Dan.
