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 23:04:51 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

------------------------------------------------------------------------------
   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.
  
- = Functional Specification for New maven.xml [INCOMPLETE DRAFT] =
+ = Functional Specification =
  
  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. 
  
@@ -31, +31 @@

  
  These are the major custom goals of maven.xml:
  
-  *runtck.jdori
-  *runtck.iut
-  *installSchema
-  *enhance.jdori
-  *enhance.iut
-  *package
+  *runtck.jdori - runs the TCK on the JDO Reference Implementation
+  *runtck.iut - runs the TCK on the implementation under test
+  *installSchema - installs the database schema
+  *enhance.jdori - enhances the class files using the JDO RI enhancer
+  *enhance.iut - enhances the class files using the implementation under test's enhancer
+  *package - packages the class, jdo, orm, and test data files into jar files
  
  == Configuration Files ==
  
@@ -84, +84 @@

  
  == 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.
+ 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 to force schema installation.
  
  == Packaging ==
  
@@ -110, +110 @@

  
  The exclude list is passed to the java test runner.
  
+ 
+ = Design =
+ 
+ == Flow Control ==
+ 
+ The language elements that control the looping and decisions in maven.xml are from the jelly
core and util packages (http://jakarta.apache.org/commons/jelly/tags.html, http://jakarta.apache.org/commons/jelly/libs/util/tags.html)

+ 
+ == Organization of Maven Goals ==
+ 
+ There are two design changes from the previous version of maven.xml:
+ 
+  1. Each goal that requires iteration has setProperties as a prerequisite goal. setProperties
parses the command line and/or configuration files and sets properties.
+ 
+  1. Each goal that requires iteration contains one or more forEach loops.  The inner loop
invokes another target that does the actual work.
+ 
  = Legacy Discussion =
  
  Below are the ideas we discussed before settling on the current solution.

Mime
View raw message