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, 21 Jun 2005 17:30:45 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 =
- An official TCK run requires running all relevant tests in all configurations that are supported
by the Implementation Under Test (IUT). For example, if the JDO implementation supports application
identity and datastore identity and supports MySQL and Derby, then the qualifying TCK test
run must test the entire configuration list (less automatically excluded tests) against application
identity and datastore identity for both MySQL and Derby.
+ An official TCK run requires running all relevant tests in all configurations that are supported
by the Implementation Under Test (IUT). For example, if the JDO implementation supports application
identity and datastore identity and supports MySQL and Derby, then the qualifying TCK test
run must test the entire configuration list (less automatically excluded tests) against application
identity and datastore identity for both MySQL and Derby. When we add different mappings for
Chapter 18 (ORM) tests, the same test will also need to be run with different mappings.
  
  While developing the JDO implementation and removing bugs, it is useful to run a subset
of configurations. This should be easily supported as well. For example, it should be easy
to run just a few tests against application identity on MySQL.
   
- 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.
+ This project involves rewriting maven.xml so that the same TCK tests can be run in multiple
configurations.
  
  = Requirements =
-  1. Developers must be able to run the JDORI (JPOX) out of the box, and later when desired,
without changing anything, simply by invoking a specific maven goal.
-  1. The TCK development team must be able to specify all of the following configuration
parameters: 
+  1. The TCK development team must be able to define the following configuration parameters
for each TCK test: 
  
   *Test description string
  
@@ -19, +18 @@

  
   *Security on/off
  
+  1.#2 Developers must be able to run the TCK on the JDORI (JPOX) out of the box, and later
on the IUT, without changing anything, simply by invoking a specific maven goal.
+ 
-  1.#2 The JDO implementation team must be able to run a subset of the above configurations
in various environments:
+  1. The JDO implementation team must be able to run a subset of the above configurations
in various environments:
   *Application identity / Datastore identity
  
   *Mapping file (.orm) (different databases need different .orm files)
  
-  1.#3 To configure a test run, users should be able to set all configuration parameters
in a text file. 
+  1.#4 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.
   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.
@@ -59, +60 @@

            *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
-         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
- 
   *exclude.list
          A list of test classes NOT to execute during a TCK test run
  
  '''Questions:'''
-  1. Do we need to allow for separate database and identity lists for the iut and jdori?
Craig says no. What do you think?
-  1. Do we assume that in general the configurations files will not be changed and users
will override them with the command line options (below)? Craig says yes. This will be part
of the "JDO TCK run rules". But we need to allow users to add their specific configuration
files to just run what they want during testing.
   1. Currently we have two properties in project.properties that can be used to specify the
implementation's support for application or datastore identity.  Should we use these instead
of the identity.list file, allowing override only on the command line? Craig thinks that we
should use the "jdori" entries when running the jdori maven goals, and use the "iut" entries
when running the iut maven goals.
  
  == Command Line Options ==
@@ -83, +76 @@

          Overrides the project.properties by supplying one or more space-separated identity
types (applicationidentity or datastoreidentity) to use for this run. Without this option,
running the runtck goal will run both if the implementation supports both.
      -DinstallSchema=<true | false>
          Defaults to false.  Set to true to force schema installation before running tests.
+ 
+ == Databases ==
+ 
+ The property jdo.tck.dblist contains a list of databases supported. The property is set
in project.properties and can be overridden on the maven command line. 
+ 
+ == Identity Types ==
+ 
+ The property jdo.tck.identitytypes contains a list of identity types to be run. The property
is set in project.properties and can be overridden on the maven command line. 
  
  == build and rebuild Goals ==
  
@@ -118, +119 @@

  == 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 ==
- 
- See question 3 in the Configuration Files section.
  
  == Security ==
  

Mime
View raw message