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 Tue, 20 Sep 2005 22:33:24 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:

The comment on the change is:
Added TOC

+ = The JDO 2.0 Technology Compatibility Kit =
+ [#About About the Technology Compatibility Kit][[BR]]
+ [#ToDo TCK ToDo][[BR]]
+ [#TestingStrategy The Testing Strategy][[BR]]
+ [#HowTo How to Develop a Test][[BR]]
+ [#Assertions JDO TCK Assertions][[BR]]
+ [#Guidelines Guidelines for Writing Test Code][[BR]]
+  [#Cleanup Cleanup][[BR]]
+ [#Cfg Configuration Files, Schemas, Metadata, and XML Test Data][[BR]]
+ [[Anchor(About)]]
  = 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.
+ [[Anchor(ToDo)]]
  = 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
@@ -18, +31 @@

   ||AllTheOtherTests||Tests of new JDO 2 features, other than query or metadata||Karan Malhi,
   ||TechnologyCompatibilityKit||Write a description of how to write a test case||Michelle
Caisse||9/05 in progress||
+ [[Anchor(TestingStrategy)]]
  = About the Testing Strategy =
  There are several variables involved in testing a relational JDO implementation:
   *the database schema,
@@ -29, +43 @@

  It is a design goal of the TCK to reduce the number of permutations of these variables.
 In order to minimize the number of database schemata, the TCK aims to generate, via a DDL
generator, any database schemas required.  It is not expected that the first version of the
JDO 2.0 TCK will include such a generator.  Until such time, database schemata will be maintained
manually.  In an effort to eliminate the number of vendor-specific database products, SQL92
will be used to express the database schemata, and implementations will be able to test their
conformance against any number of database vendors' products.  We have not yet determined
to what degree variations from the TCK's schemata will affect conformance test results.
+ [[Anchor(HowTo)]]
  = How to Develop a Test =
  These instructions assume that you already know how to check out the JDO repository.  See
SubversionRepository for more information.
@@ -88, +102 @@

   1. Make changes as agreed upon by the community.  When all changes are complete, submit
the patch for check-in.
   1. Update the   [http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/jdo/trunk/tck20/assertions/JdoTckAssertionsTable.sxc
assertions spreadsheet] with your test information. Change the Implemented column to "yes"
and add the test path and name to the Test column.
+ [[Anchor(Assertions)]]
  = JDO TCK Assertions =
  The JDO team went through the JDO specification and identified assertions the JDO TCK needs
to test. An assertion consists of an assertion number and the corresponding text of the JDO
specification describing what the test class needs to check. Usually an assertion is implemented
by one JDO TCK test class and the test class covers one assertion. There is an assertion spreadsheet
listing all the assertions with their number, text and whether they are already implemented
in the current version of the JDO TCK. This assertion overview is organized in multiple sheets,
one sheet per chapter of the JDO specification. You find the current version of the spreadsheet
@@ -106, +122 @@

  Download the current version of the  [http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/jdo/trunk/tck20/assertions/JdoTckAssertionsTable.sxc
assertions spreadsheet].
  It is in Star``Office/Open``Office format. This version adds new assertions to the query
chapter covering JDOQL extensions in JDO 2.0. Furthermore it updates the assertions about
+ [[Anchor(Guidelines)]]
- = Guidelines for Writing the Test Code =
+ = Guidelines for Writing Test Code =
  Use the [http://wiki.apache.org/geronimo/CodingStandards coding standards] of the Geronimo
  See the annotated SampleTest for pointers on how to write test code.
+ [[Anchor(Cleanup)]]
  == Cleanup ==
  Each test in the TCK must leave the datastore clean when it exits.
@@ -137, +155 @@

  '''Note''': The order of adding tear down instances and classes is significant. The default
implementation of "localTearDown" first deletes  all added instances in exactly that order
they have been added. Afterwards it deletes the extents of all classes in exactly that order
they have been added.
+ [[Anchor(Cfg)]]
  = Configuration Files, Schemas, Metadata, and XML Test Data =
  Read this section if you are writing a test that requires xml test data (like org.apache.jdo.tck.mapping.CompletenessTest)
or requires a new mapping and schema.

View raw message