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."
Not that I'm saying that's a bad idea, I think it's great, and maybe we
can provide some template code for our users who are using Derby for
unit testing. But it doesn't remove the fact that database startup is
slow (except for on Dag's machine :)).
David
Daniel John Debrunner wrote:
David Van Couvering wrote:
I personally haven't seen a problem either (except that derbyall takes
for bloody ever).
Easy way to fix that, get involved in the effort to switch to JUnit. :-)
http://wiki.apache.org/db-derby/KillDerbyTestHarness
Dan.
