db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "KillDerbyTestHarness" by DanDebrunner
Date Thu, 27 Jul 2006 14:19:24 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DanDebrunner:
http://wiki.apache.org/db-derby/KillDerbyTestHarness

------------------------------------------------------------------------------
  
   || '''Feature''' || '''Decorator''' || '''JIRA''' || '''Comments''' ||
   || Create & remove database || yes || [http://issues.apache.org/jira/browse/DERBY-1557
DERBY-1557] || ||
-  || Setup !SecurityManager and policy file || yes(?) || || ||
+  || Setup !SecurityManager and policy file || no & yes || || Messing around with this
it seems the best way is to have !BaseTestCase install a security manager with the default
policy and have decorators to remove the security manager or change the policy file for individual
tests. Then a large number of decorators are not needed to run the tests and the exception
cases (no security manager, separate policy file) will stand out. Adding a class `functionTests.util.SecurityManagerSetup`
||
   || Cleanup database objects || yes || [http://issues.apache.org/jira/browse/DERBY-1556
DERBY-1556] || '''new''' - allows databsaes to be shared across tests to decrease test running
time ||
   || Determine JDK environment || no || || E.g. isFoundation() etc., is JDK 1.3 ||
   || Boot & shutdown network server || yes || || At least within the same JVM can be
a decorator ||

Mime
View raw message