db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From banda...@apache.org
Subject svn commit: r165211 - /incubator/derby/code/trunk/java/testing/README.htm
Date Thu, 28 Apr 2005 22:01:21 GMT
Author: bandaram
Date: Thu Apr 28 15:01:20 2005
New Revision: 165211

URL: http://svn.apache.org/viewcvs?rev=165211&view=rev
Update README file in testing directory, with information on how to run tests with Derby client.

Submitted by Myrna Van Lunteren (m.v.lunteren@gmail.com)


Modified: incubator/derby/code/trunk/java/testing/README.htm
URL: http://svn.apache.org/viewcvs/incubator/derby/code/trunk/java/testing/README.htm?rev=165211&r1=165210&r2=165211&view=diff
--- incubator/derby/code/trunk/java/testing/README.htm (original)
+++ incubator/derby/code/trunk/java/testing/README.htm Thu Apr 28 15:01:20 2005
@@ -13,7 +13,7 @@
 <small>created by myrna@golux.com<br>
-last updated on 12/02/2004 by: myrna@golux.com<br>
+last updated on 04/18/2005 by: m.v.lunteren@gmail.com<br>
@@ -90,7 +90,9 @@
 Before you can run, you need to setup your environment:<br>
-  <li>Obtain a jdk or jre (based on jdk 1.3.1 specification or higher).
+  <li>Obtain a jdk or jre (based on jdk 1.3.1 specification <small><a
+ href="README.htm#Note1:"><small>See Note1</small></a></small>
 Add the bin directory to your $PATH. Currently supported are:<br>
@@ -134,8 +136,10 @@
     <small>&nbsp;&nbsp;&nbsp; derby tools classes for tools like ij
 and dblook</small><li><small>derbynet.jar<br>
-    <small>&nbsp;&nbsp;&nbsp; derby network server classes</small><li><small>db2jcc.jar
-and db2jcc_license_c.jar <br>
+    <small>&nbsp;&nbsp;&nbsp; derby network server classes</small><li><small>derbyclient.jar<br>
+      </small></li>
+    <small>&nbsp;&nbsp;&nbsp; derby client classes</small><li><small>db2jcc.jar
+and db2jcc_license_c.jar<br>
     <small>&nbsp;&nbsp;&nbsp; IBM Universal JDBC Driver classes. (See
 IBM <a href="http://www-106.ibm.com/developerworks/db2/downloads/jcc/">developerworks</a>
@@ -158,12 +162,14 @@
       <td style="vertical-align: top;"><small>(note that $jardir is
-only a convenience variable and that the command below has carriage
+only a convenience variable and that the set CLASSPATH command below
+has carriage
 returns for formatting reasons):<br>
       </small><small>set jardir=/local/derbyjar<br>
@@ -205,12 +211,13 @@
-To run a test with network server, add -Dframework=DerbyNet to the run.
+To run a test with network server, using the derbyclient driver, add
+-Dframework=DerbyNetClient to the run.
 The test harness will to start
 network server at port 1527 or connect to a running one, run the test,
 and stop network server thereafter.<br>
 for example:<br>
-&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; java </small><small>-Dframework=DerbyNet
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; java </small><small>-Dframework=DerbyNetClient
       </small><small> </small></td>
@@ -275,16 +282,24 @@
     <li>tested on a variety of hardware takes from 1.15m to 2.00 hours<br>
+  <li>derbynetclientmats</li>
+  <ul>
+    <li>basic network server tests using the derby client<br>
+    </li>
+    <li>variety of tests, including some from derbylang suite</li>
+    <li>tested on a variety of hardware takes from 15 to 30 minutes</li>
+  </ul>
-    <li>basic network server tests.</li>
+    <li>basic network server tests using the IBM Universal JDBC driver<br>
+    </li>
     <li>variety of tests, including some from derbylang suite</li>
     <li>tested on a variety of hardware takes from 15 to 30 minutes</li>
-    <li>tests networkserver functionality without requiring
-networkserver framework<br>
+    <li>tests network server functionality without requiring
+network server framework<br>
@@ -437,7 +452,7 @@
     <li>tested on a variety of hardware takes from 3.00 - 6.00 hours </li>
-  <li><a href="#Note1:"><small>See Note1</small></a><br>
+  <li><a href="#Note2:"><small>See Note2</small></a><br>
@@ -548,9 +563,8 @@
 <p>See section 2.1 for the basic steps to run 1 test.
 <p>To pass on system level properties to the test harness, use the test
-harness property -DtestSpecialFlags. For
-example, to run a test forcing
-the message text to be retrieved from the network server:
+harness property -DtestSpecialFlags. For example, to ensure extra
+information is appended to the log:&nbsp;<br>
  style="text-align: left; width: 558px; height: 32px; margin-left: 40px;"
@@ -558,8 +572,8 @@
       <td style="vertical-align: top;"> <small>java
@@ -568,9 +582,10 @@
 Tests will be executed in the current directory. When
 running a test
-using the network server, i.e. -Dframework=DerbyNet, the test will run
-in a subdirectory (automatically created) 'DerbyNet'. <small> <br>
-<a href="#Note2:">See Note2</a>.<br>
+using the network server and derby client, i.e.
+-Dframework=DerbyNetClient, the test will run
+in a subdirectory (automatically created) 'DerbyNetClient'. <small> <a
+ href="#Note3:"></a><br>
 The test will normally create the following:<br>
@@ -604,7 +619,7 @@
 When the test is successful, cleanup will occur unless the test harness
 property -Dkeepfiles=true is used. Cleanup will attempt to cleanup all
 files except for .pass. <small><br>
-<a href="#Note3:_">See Note3.</a></small>
+<a href="#Note3:">See Note3.</a></small>
 A successful run (this example is from a dos environment) would
@@ -840,7 +855,8 @@
 For example, if we are running a test and the flag -Dframework=DerbyNet
-is used and the jvm we are
+is used, to use network server and the IBM Universal JDBC Driver
+('jcc'), and the jvm we are
 using is Sun's jdk 142, and the jcc version is 2.4 (not available at
 time of writing) then the search for the master to compare with
 starts in the functionTests/derbynet/jcc2.4/jdk14 directory. If a .out
@@ -956,7 +972,7 @@
       <td style="vertical-align: top;"><small>-----------------------derbyall.properties---------------<br>
-suites=derbylang derbynetmats storeall xa derbytools<br>
+suites=derbylang derbynetclientmats derbynetmats storeall xa derbytools<br>
@@ -965,7 +981,8 @@
 The derbylang suite is only a derbylang.runall, which lists the tests.
-The derbynetmats suite has both a .runall and a .properties file, so
+The derbynetclientmats suite has both a .runall and a .properties file,
 some additional properties can be specified that are true for all tests
 in that suite. </p>
@@ -973,9 +990,9 @@
  border="1" cellpadding="2" cellspacing="2">
-      <td style="vertical-align: top;"><small>------------------derbynetmats.properties-----------------<br>
+      <td style="vertical-align: top;"><small>------------------derbynetclientmats.properties-----------------<br>
+suites=derbynetclientmats derbynetmats<br>
@@ -1066,8 +1083,7 @@
 The skip setting does not go into the subversion level, i.e. setting
 runwithjdk141=false has no effect, and setting runwithjdk14 affects
 runs with jdk141 as well as jdk142.<br>
-Other skip reasons are encryption protocols specific to a certain
+Other skip reasons are encryption protocols specific to a certain jvm. <br>
 <p>The property for skipping a test based on the version of the IBM
 Universal Driver is "excludeJCC".&nbsp; The keywords "<span
@@ -1099,9 +1115,9 @@
 Driver that is 2.0 or earlier, but ONLY if the jvm is 1.5 or later:<br>
 <p>Another skipping mechanism works on entire 'frameworks'. Currently
-there are only 3 supported in the harness, embedded, NetworkServer with
-the IBM Universal JDBC Driver ('DerbyNet') and NetworkServer with the
-not yet available new driver ('DerbyNetClient'). In the suites
+there are only 3 supported in the harness, embedded, network server
+with the derbyclient driver ('DerbyNetClient') and network server with
+the IBM Universal JDBC Driver ('DerbyNet'). In the suites
 directory there are .exclude files for each of the frameworks - if for
 some reason an exclude file were not there, you would see a warning
 message show up for every test run. In this 'framework'.exclude file
@@ -1114,13 +1130,17 @@
 <h3><a name="frameworks"></a>4.11 Frameworks</h3>
-Currently, the only framework used is DerbyNet for network server. <br>
-Setting framework property setting will invoke the test harness class
-NetServer, which currently has configuration for connecting to DB2 via
-jcc (the IBM Universal Driver), and via the older db2 driver. But there
-are currently no tests to exercise these settings.<br>
+Currently, there are two frameworks used for network server,&nbsp;<span
+ style=""></span><span class="SpellE"></span><span class="SpellE">DerbyNetClient</span>,
+which uses the derby Client driver, and DerbyNet, which uses the IBM
+Universal JDBC Driver. <br>
+Setting the framework property will invoke the test harness class
+NetServer which has the actual configuration (driver name, portnumber
+etc.) used for the individual frameworks. <small><a
+ href="README.htm#Note3:">See Note4.</a></small><br>
 Setting this framework also causes the search for expected output to
-include DerbyNet and jcc version specific subdirectories under master.<br>
+include appropriate DerbyNetClient or&nbsp; DerbyNet and jcc version
+specific subdirectories under the master directory.<br>
 <h3><a name="props"></a>4.12 Some test harness properties</h3>
@@ -1138,7 +1158,8 @@
 section <a href="#skipping">4.10</a><br>
 &nbsp;&nbsp;&nbsp; specifies which framework to run with. For example:<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; java -Dframework=DerbyNet
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; java
 org.apache.derbyTesting.functionTests.RunTest <br>
@@ -1154,7 +1175,7 @@
 &nbsp;&nbsp;&nbsp; sets additional properties.<br>
 &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; java
-org.apache.derbyTesting.functionTests.RunTest lang/arithmetic.sql<br>
+org.apache.derbyTesting.functionTests.RunTest lang/arithmetic.sql <br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; See above section
@@ -1164,12 +1185,18 @@
-<small><a name="Note1:"></a> Note1:<br>
+<small><a name="Note1:"></a>Note1:<br>
+<div style="margin-left: 40px;"><small>A number of tests require
+packages that are optional with jdk13, but included with later jvms:
+jdbc20ext.jar and jta1_2.jar</small><small>. When running with jdk131,
+these need to be downloaded separately &amp; placed in the jre/lib/ext
+directory of your jvm installation.</small><br>
+<a name="Note2:"></a> Note2:<br>
 <div style="margin-left: 40px;"><small>There is one more suite
 included: the j9derbynetmats
@@ -1190,34 +1217,28 @@
 on the executable, j9.exe), based on the property 'serverJvm'. Running
 this suite requires providing the property&nbsp; bootcp,
 which is&nbsp; interpreted from the test harness class j9_13. See also
-section on adding a new <a href="#ov9%22">jvm setup</a>.
+section on adding a new <a href="#ov9">jvm setup</a>.
-Another suite is derbynetclientmats. This suite is for testing the
-networkserver with a yet to be contributed open source client. IBM
-staff is working on contributing this. In essence it is the same as the
-derbynetmats suite.&nbsp; At this time, it can only be run by the IBM
-staff working on this driver.<br>
-<small><a name="Note2:"></a>Note2:<br>
+<small><a name="Note3:"></a>Note3:<br>
-<div style="margin-left: 40px;"><small>setting
-RetrieveMessagesFromServerOnGetMessage to true
-for the test harness is purely for
-illustration, the test harness actually forces
-RetrieveMessagesFromServerOnGetMessage to true for the tests so the
-output is always as expected.</small><br>
-<small><a name="Note3:_"></a>Note3: <br>
-<div style="margin-left: 40px;"><small>occasionally, cleanup is
+<div style="margin-left: 40px;">O<small>ccasionally, cleanup is
 unsuccessful. This does not
-constitute a problem in any way, as the harness starts with a clean
+constitute a problem in any way, as the harness for most suites starts
+with a clean
 database, and clean copies of all files. However, you will see
 something like this in the output:</small><br>
 <small>Warning: Cleanup failed on baseDir:
+<small><a name="Note4:_"></a>Note4: <br>
+<div style="margin-left: 40px;"><small>NetServer also has a
+configuration for connecting to DB2 via jcc - the IBM Universal Driver
+- and via the older DB2 driver. But there are currently no tests to
+exercise these settings.</small><br>

View raw message