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] Trivial Update of "KillDerbyTestHarness" by MyrnavanLunteren
Date Tue, 13 Feb 2007 20:20:58 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 MyrnavanLunteren:
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 || 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 ||
+  || Cleanup database objects || yes || [http://issues.apache.org/jira/browse/DERBY-1556
DERBY-1556] || '''new''' - allows databases to be shared across tests to decrease test running
time ||
   || Determine JDK environment || no ||  [http://issues.apache.org/jira/browse/DERBY-1638
DERBY-1638] for JDBC level || E.g. isFoundation() etc., is JDK 1.3 ||
   || Boot & shutdown network server || yes || [http://issues.apache.org/jira/browse/DERBY-1712
DERBY-1712]|| At least within the same JVM can be a decorator||
   || Setup & remove extin, extout, extout folders || yes ||(see [http://issues.apache.org/jira/browse/DERBY-1656
DERBY-1656] )  || ||
   || Copy & remove support files  || yes || || In some cases files can be accessed directly
as resources instead of copying them. See the test resource methods in `BaseTestCase` ||
   || Set & clear derby properties || yes || || Replacement for the <test>_derby.properties,
system properties implemented in class `SystemPropertyTestSetup` ||
   || Shutdown database/server || no || [http://issues.apache.org/jira/browse/DERBY-1826 DERBY-1826]
|| ||
+  || Support running junit tests directly with a remote server || no || [http://issues.apache.org/jira/browse/DERBY-1973
DERBY-1973] || ||
  
  == Folder Policy ==
  It would be good to have some up-front policy about how folders are used, to provide consistency
and help with good security manager testing. See:

Mime
View raw message