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 "DerbyJUnitTesting" by MyrnavanLunteren
Date Wed, 02 Jan 2008 16:27: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 MyrnavanLunteren:

  <!> No system properties are required when running directly with !TestRunners, the
!BaseTestCase class
  automatically installs a security manager with the correct policy file.
+ However, the following ad hoc system properties may be beneficial in specific cases:
+   * `derbyTesting.oldReleasePath` : this property applies only to the upgradeTests suite,
and then specifies the location where old release (derby.)jars can be found. More details
can be found in the javadoc for the upgradeTests, but when running these tests regularly,
or when running them behind a firewall, you should, respectively need to download the jars
and specify the property. When the property is not specified, the (upgrade)tests will attempt
to connect to the svn repository.
+   * `derby.tests.trace` : when this value is set to true, output is generated that reflects
each test and the time it took to run; this is useful when running with taciturn testrunners,
such as the `junit.textui.TestRunner` (which otherwise only prints a '.' for each fixture).
The default value is off.
+   * `derby.tests.debug` : switches on verbose running. Any tests that have taken advantage
of the method `org.apache.derbyTesting.junit.TestConfiguration.println()` will print additional
statements when this is switched to true. Default value is off.
  See some notes on running test runners on [:JunitVmIssues: specific platforms] including
WCTME 5.7.
  ==== batch run ====

View raw message