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 "TechnologyCompatibilityKit" by MichelleCaisse
Date Wed, 14 Sep 2005 16:01:58 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/TechnologyCompatibilityKit

The comment on the change is:
minor edits, reorg

------------------------------------------------------------------------------
  = About the Technology Compatibility Kit =
  The JDO Technology Compatibility Kit (TCK) tests that a JDO implementation is in compliance
with the standard. This page contains information for developers of the JDO 2.0 TCK.
+ 
+ = TCK ToDo =
+ 
+ This is the list of tasks required to complete the JDO 2.0 TCK. We welcome new contributors!
If you wish to contribute, please send email to [mailto:jdo-dev@db.apache.org jdo-dev@db.apache.org].
See [http://incubator.apache.org/jdo/mail-lists.html Apache JDO Mailing Lists] for subscription
information.
+  ||Activity wiki page||Description||Who||Expected Completion Date||
+  ||TestRunner||Rewrite 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.||Michelle
Caisse||6/10/05 done||
+  ||["XMLMetadata"]||Develop xml metadata tests (Chapter 18)||Michelle Caisse, Michael Watzek
& others||?/05||
+  ||QueryTests11||Finish JDO 1 TCK query test classes||Michael Bouschen||done March 05||
+  ||QueryTests||Write tests for the query language enhancements and new query api's||Michael
Bouschen, Michael Watzek||?/05||
+  ||DetachedObjects||Design and write tests for detached objects||Matthew Adams||?/05||
+  ||--||Rewrite examples in Chapter 15 to use the Company model; associate each example with
a specific test case via assertion conditional text.||Craig Russell||?/05||
+  ||RunRules||Write the rules vendors must follow in running the TCK to demonstrate compliance
with the specification||Craig Russell||9/05||
+  ||--||Complete the list of assertions from the Proposed Final Draft, create wiki page listing
assertions needing to be implemented||Michelle Caisse||9/05 in progress||
+  ||AllTheOtherTests||Tests of new JDO 2 features, other than query or metadata||Karan Malhi,
others||?/05||
+  ||TechnologyCompatibilityKit||Write a description of how to write a test case||Michelle
Caisse||9/05 in progress||
  
  = About the Testing Strategy =
  There are several variables involved in testing a relational JDO implementation:
@@ -40, +55 @@

  
    PC_CLASS - The name of the persistence capable class instantiated.  If none, delete localSetUp().
If more than one, add additional addTearDownClass(PC_CLASS.class) invocations.
  
-  6. Decide which test superclass to extend for this test. If your test belongs to a package
with its own superclass, you would use it. Check what class other test classes in the package
extend. Otherwise you would extend org.apache.jdo.tck.JDO_Test. If you are starting a new
package, consider whether there are methods or fields that you can factor into a new class
which you would extend.
+  6. Decide which test superclass to extend for this test. If your test belongs to a package
with its own superclass, use it. Check what class other test classes in the package extend.
Otherwise extend org.apache.jdo.tck.JDO_Test. If you are starting a new package, consider
whether there are methods or fields that you should factor into a new class which you would
extend.
-  1. Choose existing persistence capable classes from org/apache/jdo/tck/pc/* if your test
requires instantiating a pc class. If no existing pc classes are suitable for your test, see
Writing a Persistence Capable Class, below..
+  1. If your test requires instantiating a pc class, choose one or more existing persistence
capable classes from org/apache/jdo/tck/pc/*. If no existing pc classes are suitable for your
test, see Writing a Persistence Capable Class, below.
   1. Write the test (see Guidelines for Writing Test Code, below).
-  1. If the test requires, provide a schema file, mapping file, xml test data, and a configuration
file (see Configuration Files, Schemas, Metadata, and XML Test Data, below). Otherwise, write
a temporary configuration file for debugging and add an entry to alltests.conf for this test.
The temporary configuration file will look like this:
+  1. If the test requires, provide a schema file, mapping file, xml test data, and a configuration
file (see Configuration Files, Schemas, Metadata, and XML Test Data, below). Otherwise, write
a temporary configuration file for debugging and add an entry to alltests.conf for this test.
The temporary configuration file looks like this:
    {{{
  jdo.tck.description = Run one test for debugging
  jdo.tck.testdata = 
@@ -91, +106 @@

  
  = Guidelines for Writing the Test Code =
  
- Use the [http://wiki.apache.org/geronimo/CodingStandards coding standards] used on the Geronimo
Project.
+ Use the [http://wiki.apache.org/geronimo/CodingStandards coding standards] of the Geronimo
Project.
  
  (more content to be provided)
  
@@ -136, +151 @@

  
  (content to be provided)
  
- = TCK ToDo =
- 
- This is the list of tasks required to complete the JDO 2.0 TCK.
-  ||Activity wiki page||Description||Who||Expected Completion Date||
-  ||TestRunner||Rewrite 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.||Michelle
Caisse||6/10/05 done||
-  ||["XMLMetadata"]||Develop xml metadata tests (Chapter 18)||Michelle Caisse & others
TBD||?/05||
-  ||QueryTests11||Finish JDO 1 TCK query test classes||Michael Bouschen||done March 05||
-  ||QueryTests||Write tests for the query language enhancements and new query api's||Michael
Bouschen||?/05||
-  ||DetachedObjects||Design and write tests for detached objects||Matthew Adams||?/05||
-  ||--||Rewrite examples in Chapter 15 to use the Company model; associate each example with
a specific test case via assertion conditional text.||Craig Russell||?/05||
-  ||RunRules||Write the rules vendors must follow in running the TCK to demonstrate compliance
with the specification||Craig Russell||9/05||
-  ||AllTheOtherTests||Complete the list of assertions from the Proposed Final Draft, create
wiki page listing assertions needing to be implemented||Michelle Caisse||9/05 in progress||
-  ||TechnologyCompatibilityKit||Write a description of how to write a test case||Michelle
Caisse||9/05 in progress||
- 

Mime
View raw message