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 "DerbyJunitTestConfiguration" by DanDebrunner
Date Thu, 05 Oct 2006 17:31:03 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/DerbyJunitTestConfiguration

------------------------------------------------------------------------------
  = Test Configurations =
  This is about test configurations in a pure JUnit setup (the eventual goal).
+ [[TableOfContents]]
  
  == Goals ==
   * Ideally running the Derby tests should allow multiple configurations to exist concurrently,
for example to parallelize test runs or stress test by kicking off multiple runs within the
same JVM.
@@ -51, +52 @@

  || '''Folder''' || '''Description''' ||
  || `system` || Location of `derby.system.home` when set. ||
  || `databases` || Location of databases when `derby.system.home` not set. This will allow
clear policy files so that user code does not have permission to write into the databse folders.
||
+ || `logs` || Location of any log files generated by the tests ||
  || `extin, extout, extinout` || Location of input files, output files or files used for
both input and output for tests. ||
  || `fail` || Top level folder to store failure information ||
  || `fail/embedded` || Failures for tests with embedded configuration ||
  || `fail/client` || Failures for tests with Derby client configuration ||
  || `fail/db2client` || Failures for tests with DB2 client configuration ||
  
- == Default Configuration ==
+ == Default Configuration (embedded) ==
  The default configuration is:
   * Embedded driver
   * `derby.system.home=${user.dir}/system`
@@ -66, +68 @@

  
  In general tests should not rely on the user name or the database name, this will allow
tests to run in multiple configurations without changes.
  
+ == Derby Client Configuration ==
+ Setup by decorator created by `TestConfiguration.derbyClientServerDecorator` static methods.
+ Inherits configuration setup from current configuration but:
+  * Uses client driver
+  * Starts network server in its setUp method, server output in `${user.dir}/logs/serverConsoleOutput.log`.
+ Note network server is not shutdown by the decorator. It is left up for future sets of tests.
+ 

Mime
View raw message