db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jdo Wiki] Update of "TestRunner" by MichelleCaisse
Date Wed, 01 Jun 2005 17:33:03 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jdo Wiki" for change notification.

The following page has been changed by MichelleCaisse:
http://wiki.apache.org/jdo/TestRunner

------------------------------------------------------------------------------
  = About TestRunner =
- This project is about extending the TCK extensions of the JUnit test runners so that the
same TCK tests can be run in multiple configurations. For example, the same TCK test program
needs to be run with and without security turned on, and with Application Identity and Datastore
Identity. When we add different mappings for Chapter 18 (ORM) tests, the same test will need
to be run with security, identity, and different mappings. W envision the test runner reading
parameters from a configuration file.
+ This project involves rewriting maven.xml so that the same TCK tests can be run in multiple
configurations. For example, the same TCK test program needs to be run with and without security
turned on, and with application identity and datastore identity. When we add different mappings
for Chapter 18 (ORM) tests, the same test will also need to be run with different mappings.
  
  = Requirements =
   1. The user must be allowed to set all of the following configuration parameters: 
  
-  Test description string
+  *Test description string
  
-  Test class
+  *Test class
  
-  Security on/off
+  *Security on/off
  
-  Application identity / Datastore identity
+  *Application identity / Datastore identity
  
-  Mapping file (.orm)
+  *Mapping file (.orm)
  
-  Test data
+  *Test data
  
-  1.#2 To configure a test run, users should be able to set all configuration parameters
in a text file, probably an xml file. 
+  1.#2 To configure a test run, users should be able to set all configuration parameters
in a text file. 
-  1. In the configuration file the user must be able to specify either a single test or a
list of tests to be run with a given set of configuration parameters.
+  1. The user must be able to specify either a single test or a list of tests to be run with
a given set of configuration parameters.
   1.  The user must be able to specify multiple configuration settings within one configuration
file, each to be run with one or more test cases.
   1. Each test execution must report the full set of parameters, as listed above.
  
- = Implementation Issues =
+ = Functional Specification for New maven.xml [INCOMPLETE DRAFT] =
+ 
+ In the current proposal, configuration parameters are set either in configuration files
or on the maven command line.  There are no separate goals for different configurations. 
+ 
+ == Custom Goals ==
+ 
+ These are the custom goals that might typically be invoked from the command line:
+ 
+  *runtck.jdori
+  *runtck.iut
+  *installSchema
+  *enhance.jdori
+  *enhance.iut
+ 
+ == Configuration Files ==
+ 
+ Maven looks for the following configuration files in test/conf:
+ 
+  *configurations.list
+         A list of files. Each file listed is a test configuration
+         file.
+ 
+  *test configuration files
+         Each of these files sets values for
+           *jdo.tck.testdescription - an optional string describing the purpose of these
tests
+           *jdo.tck.classes - a list of one or more test classes.
+           *jdo.tck.testdata - fully qualified file name (not required by all tests)
+           *jdo.tck.mapping - file designator that maven.xml uses to build a javax.jdo.option.Mapping
value and corresponding schema name
+ 
+  *database.list
+         A list of one or more databases to run the TCK on.
+ 
+  *identity.list
+         A list of one or two identity types to run the TCK on.
+ 
+ == Command line options ==
+ 
+     -Dcfg=<configuration file>
+         Overrides test/conf/configuration.list by supplying one or more space-separated
test configuration files
+     -Ddatabase=<database list>
+         Overrides test/conf/db.list by supplying one or more space-separated database names
+     -Didentity=<identity type list>
+         Overrides test/conf/identity.list by supplying one or more space-separated identity
types (applicationidentity or datastoreidentity)
+     -DinstallSchema=<true | false>
+         Defaults to false.  Set to true to force schema installation before running tests.
+ 
+ == build and rebuild goals ==
+ 
+ These goals do not recognize the command line options.  They do a full build and run the
TCK on the JDORI for all configurations, databases, and identity types listed in the configuration
files. [Is this a good idea?]
+ 
+ == Schema Installation ==
+ 
+ Schema installation takes a significant amount of time and it is difficult to determine
if a schema is up-to-date.  By default, maven.xml installs the schema for all databases, identity
types, and mapping values set for the current invocation only during a full build (maven build
or rebuild goals).  The user may override this behavior by using the -DinstallSchema=true
option with the runtck.jdori or runtck.iut goals.
+ 
+ == Identity Type Support ==
+ ...
+ 
+ == Exclude List ==
+ ...
+ 
+ = Legacy Discussion =
+ 
+ Below are the ideas we had before settling on the current solution.
  
  == Role of build.xml ==
  
@@ -39, +101 @@

  
  The user will be required to configure the build to specify the implementation's support
for identity types. This will prevent test failure due to lack of support.
  
- = Open Questions =
+ == Open Questions ==
   *What about nondurable identity? Currently, nondurable identity is not supported by the
RI, so we cannot verify that the TCK runs properly with it.  This situation is not likely
to change with JDO 2.0.
-  *Can the build process read parameters from the configuration file?  See section "Role
of build.xml" on this page.
  

Mime
View raw message