[Db-derby Wiki] Update of "KillDerbyTestHarness" by DanDebrunner

[Apache Wiki <wi...@apache.org>]

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

------------------------------------------------------------------------------
   || 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 ||
-  || Determine JDK environment || no || || E.g. isFoundation() etc., is JDK 1.3 ||
+  || 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 || || At least within the same JVM can be a decorator ||
   || Setup & remove extin, extout, extout folders || yes || || ||
   || Copy & remove support files  || yes || || ||
-  || Set & clear derby properties || yes || || Replacement for the <test>_derby.properties ||
+  || Set & clear derby properties || yes || || Replacement for the <test>_derby.properties, system properties implemented in class `SystemPropertyTestSetup` ||