You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by cl...@apache.org on 2006/02/25 16:57:40 UTC
svn commit: r380940 - /db/jdo/trunk/tck20/RunRules.html
Author: clr
Date: Sat Feb 25 07:57:38 2006
New Revision: 380940
URL: http://svn.apache.org/viewcvs?rev=380940&view=rev
Log:
JDO-301 Updated RunRules.html
Modified:
db/jdo/trunk/tck20/RunRules.html
Modified: db/jdo/trunk/tck20/RunRules.html
URL: http://svn.apache.org/viewcvs/db/jdo/trunk/tck20/RunRules.html?rev=380940&r1=380939&r2=380940&view=diff
==============================================================================
--- db/jdo/trunk/tck20/RunRules.html (original)
+++ db/jdo/trunk/tck20/RunRules.html Sat Feb 25 07:57:38 2006
@@ -5,7 +5,7 @@
<TITLE></TITLE>
<META NAME="GENERATOR" CONTENT="NeoOffice/J 1.1 (Unix)">
<META NAME="CREATED" CONTENT="20051228;16322200">
- <META NAME="CHANGED" CONTENT="20060124;10445500">
+ <META NAME="CHANGED" CONTENT="20060225;7555700">
<STYLE>
<!--
@page { size: 8.5in 11in }
@@ -14,27 +14,29 @@
</HEAD>
<BODY LANG="en-US" DIR="LTR">
<H1 ALIGN=CENTER>Running the JDO 2.0 Technology Compatibility Kit</H1>
-<P ALIGN=CENTER><I>DRAFT Version 0.2</I></P>
-<P ALIGN=CENTER>24-Jan-2006</P>
+<P ALIGN=CENTER><BR><BR>
+</P>
+<P ALIGN=CENTER>25-Feb-2006</P>
<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Overview</FONT></FONT></P>
<P>In order to demonstrate compliance with the Java Data Objects
specification, an implementation must successfully run all of the TCK
-tests that are not on the âexcludedâ list.
-</P>
+tests that are not on the âexcludedâ list. The implementation is
+hereinafter referred to as the IUT (Implementation Under Test).</P>
<P>The results must be posted on a publicly accessible web site for
examination by the public. The posting includes the output of the
-test run, which consists of multiple log files, configuration
-information, and results. For an example of the required posting,
-please see <A HREF="http://db.apache.org/jdo/tck/final">http://db.apache.org/jdo/tck/final</A>.</P>
+test run, which consists of multiple log files containing
+configuration information and test results. For an example of the
+required posting, please see <A HREF="http://db.apache.org/jdo/tck/final">http://db.apache.org/jdo/tck/final</A>.</P>
<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Prerequisites</FONT></FONT></P>
-<P>In order to run the TCK, you must install maven 1.0.2. M<FONT FACE="Times New Roman, serif">aven
+<P>In order to run the TCK, you must install maven 1.0.1 or 1.0.2.
+M<FONT FACE="Times New Roman, serif">aven
</FONT><A HREF="http://maven.apache.org/maven-1.x/"><FONT FACE="Times New Roman, serif"><FONT COLOR="#000000">http://maven.apache.org/maven-1.x/
</FONT></FONT></A><FONT FACE="Times New Roman, serif">is the</FONT>
driver of the test programs. Note that Maven 2 is not supported.</P>
-<P>You must test the JDO implementation on all configurations that
-the implementation supports. This includes different hardware and
-operating systems, different versions of Java, and different
-datastores. The TCK supports Java versions from JDK 1.3 to 1.5.</P>
+<P>You must test the IUT on all configurations that the IUT supports.
+This includes different hardware and operating systems, different
+versions of Java, and different datastores. The TCK supports Java
+versions from JDK 1.3 to 1.5.</P>
<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Installation</FONT></FONT></P>
<P>Download the zip file from the distribution at the Java Community
Process web site http://jcp.org/en/jsr/detail?id=243. Unpack the zip
@@ -48,22 +50,25 @@
<LI><P>maven configuration files project.properties and project.xml
(common project definition for all Apache JDO projects including
the TCK). These files must not be changed.</P>
- <LI><P STYLE="margin-bottom: 0in">lib â this directory contains a
- directory ext that should contain jar fi<FONT FACE="Times New Roman, serif">les
+ <LI><P STYLE="margin-bottom: 0.2in">lib â this directory contains
+ a directory ext that should contain jar fi<FONT FACE="Times New Roman, serif">les
<FONT COLOR="#000000">fscontext.jar and providerutil.jar </FONT>us</FONT>ed
by the JNDI tests. <FONT FACE="Times New Roman, serif"><FONT COLOR="#000000">The
jar files can be found at
</FONT></FONT><A HREF="http://java.sun.com/products/jndi/downloads/index.html"><FONT FACE="Times New Roman, serif"><FONT COLOR="#000000">http://java.sun.com/products/jndi/downloads/index.html</FONT></FONT></A><FONT FACE="Times New Roman, serif"><FONT COLOR="#000000">.
Choose "File System Service Provider, 1.2 Beta 3" from
the "Download JNDI 1.2.1 & More" page. Unzip the
- archive and install them into the lib/ext directory.</FONT></FONT></P>
+ archive and install them into the lib/ext directory. It is
+ permitted to use a different JNDI implementation; see the
+ README.txt for information on how to configure a different JNDI
+ implementation.</FONT></FONT></P>
<LI><P>the TCK directory, which has a release-specific name (e.g.
- jdo2-tck-2.0-beta) and contains:</P>
+ jdo2-tck-2.0) and contains:</P>
<UL>
<LI><P>maven.xml, project.properties, project.xml â the maven
definition of the project. These files must not be modified.</P>
<LI><P>build.properties â the maven definition for the IUT. This
- file may be modified to change any of the iut properties needed.</P>
+ file may be modified to change any of the IUT properties needed.</P>
<LI><P>this RunRules.html</P>
<LI><P>assertions â contains the assertions file identifying the
assertions tested by the tests. This is for reference.</P>
@@ -128,19 +133,21 @@
<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Running
the Tests</FONT></FONT></P>
<P>From the installation directory, change to the TCK directory. From
-the TCK directory, call maven build which will build the jar files
-used in the tests, create the Derby database, install the schema into
-the Derby database, and run the TCK on the Reference Implementation.</P>
-<P>Then call maven runtck.iut to run the tests on the Implementation
-Under Test. This will produce console output plus a directory in the
-TCK/target/logs directory with the date/time the tests were started.
-This directory contains the output of the tests. This is the
-directory to be published.</P>
+the TCK directory, call âmaven buildâ which will build the jar
+files used in the tests, create the Derby database, install the
+schema into the Derby database, and run the TCK on the Reference
+Implementation. Success indicates that the TCK was installed
+correctly.</P>
+<P>Then call âmaven runtck.iutâ to run the tests on the
+Implementation Under Test. This will produce console output plus a
+directory in the TCK/target/logs directory whose name contains the
+date/time the tests were started. This directory contains the output
+of the tests. This is the directory to be published.</P>
<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Debugging
the IUT while running TCK tests</FONT></FONT></P>
-<P>Execute the maven goal âhelpâ in the TCK directory in order to
-get information on running the TCK tests with a debugger. In
-particular, properties jdo.tck.cleanupaftertest, jdo.tck.cfglist,
+<P>Execute âmaven helpâ in the TCK directory in order to get
+information on running the TCK tests with a debugger. In particular,
+properties jdo.tck.cleanupaftertest, jdo.tck.cfglist,
jdo.tck.identitytypes, and jdo.tck.dblist may be useful.</P>
<P>If you make a change to the IUT enhancer while debugging the TCK
tests (for implementations that use an enhancer) you must remove the
@@ -152,21 +159,22 @@
the tests must be published on a publicly-available web site. The
unmodified directory is the self-certification of the successful TCK
test run.</P>
-<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>Challenging
-the Validity of a Test or Configuration</FONT></FONT></P>
-<P>If any test does not pass on the JDO implementation under test,
-this may be due to an error in the implementation or in the TCK test.
-If you believe that the failure is due to an error in the TCK test,
-you may challenge the test. To do so, send email to:
-<A HREF="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</A> with
-a subject line containing âCHALLENGEâ and the name of the test
-program, e.g.
+<P STYLE="margin-top: 0.17in; page-break-after: avoid"><FONT FACE="Albany, sans-serif"><FONT SIZE=4>First
+Level TCK Appeals Process</FONT></FONT></P>
+<P STYLE="margin-top: 0.17in; page-break-after: avoid">If any test
+does not pass on the JDO implementation under test, this may be due
+to an error in the implementation or in the TCK test. If you believe
+that the failure is due to an error in the TCK test, you may
+challenge the test. To do so, send email to: <A HREF="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</A>
+with a subject line containing âCHALLENGEâ and the name of the
+test program, e.g.
org.apache.jdo.tck.api.persistencemanager.ThreadSafe.java; and the
body of the email containing the details of the challenge.</P>
-<P>If the issue is found by the Maintenance Lead to be due to an
-error in the test case, then the test may be put into the TCK
-directory src/conf/exclude.list and it will not be run as part of the
-TCK.</P>
+<P>The Maintenance Lead will respond within 15 working days with a
+decision on whether there is an error in the test case. If the issue
+is found by the Maintenance Lead to be due to an error in the test
+case, then the test may be put into the TCK directory
+src/conf/exclude.list and it will not be run as part of the TCK.</P>
<P>Decisions of the Maintenance Lead may be appealed to the full
expert group. A vote of the full expert group will be conducted by
the Maintenance Lead, and a majority of votes cast will decide the