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 Tue, 07 Jun 2005 23:50:10 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

------------------------------------------------------------------------------
  
   *Mapping file (.orm)
  
-  *Test data
+  *Test data (both input test data and, in some cases, a standard to compare to after updates)
  
   1.#2 To configure a test run, users should be able to set all configuration parameters
in a text file. 
   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.
@@ -36, +36 @@

   *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.jdori - packages the jdori enhanced classes, jdo, orm, and test data files into
jar files
-  *package.iut - packages the iut enhanced classes, jdo, orm, and test data files into jar
files
  
  == Configuration Files ==
  
@@ -52, +50 @@

            *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.standarddata - 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
@@ -89, +88 @@

  
  == Packaging ==
  
- The files needed for test execution are packaged into four jar files:
+ The files needed for test execution are copied into four directory trees:
-  *target/enhanced/jdori/applicationidentity.jar
+  *target/enhanced/jdori/applicationidentity/
-  *target/enhanced/jdori/datastoreidentity.jar
+  *target/enhanced/jdori/datastoreidentity/
-  *target/enhanced/iut/applicationidentity.jar
+  *target/enhanced/iut/applicationidentity/
-  *target/enhanced/iut/datastoreidentity.jar
+  *target/enhanced/iut/datastoreidentity/
  
- Each of these jar files contains:
+ Each of these trees contains:
   *enhanced test classes
   *jdo metadata files
   *orm metadata files
   *xml test data files
  
- There may be multiple orm and xml files for a single persistence capable (pc) class or package.
 These are distinguished by different mapping designators in their filenames.  For example,
a given test configuration may run a set of tests on databases derby and mysql with mapping
4.  The mapping metadata files are package-derby4.orm and package-mysql4.orm; the test data
files are package-derby4.xml and package-mysql4.xml. The orm, jdo, xml, and class files are
in the same package in the jar file.
+ Currently, the jar files are created and then the directory tree is deleted.  However, the
classes have to be re-enhanced every time an orm or xml file is modified so that the jar file
can be recreated.  To avoid this, we will not delete the tree, thus there is no need to create
a jar file.
  
- Currently, the class directory tree is deleted after the jar files are created.  However,
doing so obviates the benefit of making packaging a separate goal, because the classes would
have to be re-enhanced every time repackaging is required.  Not doing so, on the other hand,
obviates the need to package the files into jar files.  Why not just put the classes tree
with metadata and test files on the classpath.  To summarize, these are the three choices:
-  1. Package and delete the class tree.  Re-enhance whenever repackaging is required.
-  1. Package and don't delete the class tree.  If the classes and jdo metadata are up to
date, re-enhancement is not required before repackaging. The class tree is redundant with
the jar files.
-  1. Don't package and don't delete the class tree.  Provide the class tree on the classpath.
+ 
+ == Mapping designator ==
+ 
+ There may be multiple orm files for a single persistence capable (pc) class or package.
 The orm files are distinguished by different mapping designators in their filenames.  For
example, a given test configuration may run a set of tests on databases derby and mysql with
mapping 4.  The mapping metadata files are package-derby4.orm and package-mysql4.orm; the
schema files are derby/schema4.xml and mysql/schema4.xml.
+ 
+ == Test Data ==
+ 
+ Test data files are xml files that define data values for one or more instances of one or
more classes in a packages.  The data is used to create in-memory data that tests may persist
and update.  If the test does not perform any updates, the test compares the retrieved persisted
data to a new instance of in-memory data.  If there are updates, the test compares the retrieved
data to an instance of a standard given in a second xml file.  The property jdo.tck.testdata
is the test data file and jdo.tck.standarddata is the standard.
  
  == Identity Type ==
  

Mime
View raw message