[Db-derby Wiki] Update of "DerbyTopLevelJunitTests" 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/DerbyTopLevelJunitTests

------------------------------------------------------------------------------
  || `org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversEmbeddedTest` ||
  || `org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversClientTest`||
  || `org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversAllTest`||
- || `org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite` || Yes || Upgrade tests, included in `suites.All` but has special requirements for accessing old released. The caller can set the system property `derbyTesting.oldReleasePath` to a folder containing previous releases. See the source comments for upgradeTests._Suite for details on how the folder is expected to look. If the property is not set then the tests will pick the old released jar files directly from Apache's SVN, if offline or the repo is not available then the tests will fail.  If the tests are to be run frequently then providing a local copy of the jars using `derbyTesting.oldReleasePath` is recommended. See the source comments for details on how to checkout the old release jar files locally. ||
+ || `org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite` || Yes || Upgrade tests, included in `suites.All` but has special requirements for accessing old released. The caller can set the system property `derbyTesting.oldReleasePath` to a folder containing previous releases. See the source comments for upgradeTests._Suite for details on how the folder is expected to look. If the property is not set then the tests will pick the old released jar files directly from Apache's SVN, if offline or the repo is not available then the tests will fail.  If the tests are to be run frequently then providing a local copy of the jars using `derbyTesting.oldReleasePath` is recommended. See the source comments for details on how to checkout the old release jar files locally.  If running the tests via the ant targets then `derbyTesting.oldReleasePath` can be set as an ant proprty, e.g. in `ant.properties` ||
  
  = System Tests =
  = Performance Tests =