river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ju...@apache.org
Subject svn commit: r745332 - in /incubator/river/jtsk/trunk/integrationtests: README.txt qatestsREADME.txt
Date Wed, 18 Feb 2009 00:51:46 GMT
Author: jukka
Date: Wed Feb 18 00:51:46 2009
New Revision: 745332

URL: http://svn.apache.org/viewvc?rev=745332&view=rev
Log:
RIVER-301: Move the tests into the JUnit framework inside the main source project

Adapted the integrationtests readme to match the current source layout.

Added:
    incubator/river/jtsk/trunk/integrationtests/README.txt
      - copied, changed from r745317, incubator/river/jtsk/trunk/integrationtests/qatestsREADME.txt
Removed:
    incubator/river/jtsk/trunk/integrationtests/qatestsREADME.txt

Copied: incubator/river/jtsk/trunk/integrationtests/README.txt (from r745317, incubator/river/jtsk/trunk/integrationtests/qatestsREADME.txt)
URL: http://svn.apache.org/viewvc/incubator/river/jtsk/trunk/integrationtests/README.txt?p2=incubator/river/jtsk/trunk/integrationtests/README.txt&p1=incubator/river/jtsk/trunk/integrationtests/qatestsREADME.txt&r1=745317&r2=745332&rev=745332&view=diff
==============================================================================
--- incubator/river/jtsk/trunk/integrationtests/qatestsREADME.txt (original)
+++ incubator/river/jtsk/trunk/integrationtests/README.txt Wed Feb 18 00:51:46 2009
@@ -1,17 +1,8 @@
 This file describes the steps one can take to build and run the tests
-provided under the 'qatests' directory of the river distribution. Note
+provided under the 'integrationtests' directory of Apache River. Note
 that the steps outlined here assume a unix or linux based system with
 access to the GNU make utility.
 
-Wherever the tokens '<jtskTrunk>' or '<qatestsTrunk>' appear in this
-document, one should take this to represent, respectively, the paths of
-the trunk in the 'jtsk' working directory and the 'qatests' working
-directory under which the river distribution has been checked out from
-subversion.
-
-For example, consider the directory paths used in the first section below,
-in which source checkout is discussed,
-
 1. CHECKOUT
 
      Suppose your home directory is /home/myUsername, and suppose you
@@ -19,14 +10,9 @@
      from the Apache River Project as show below,
 
      > cd ~
-     > svn checkout https://svn.apache.org/repos/asf/incubator/river river
-
-     then <jtskTrunk> represents /home/myUsername/river/jtsk/trunk,
-     and <qatestsTrunk> rerpresents /home/myUsername/river/qatests/trunk
-     in all commands where the corresponding token appears. When
-     using those commands in your own environment, each such token
-     should be replaced with the analogous and appropriate path for
-     your system.
+     > svn checkout \
+           https://svn.apache.org/repos/asf/incubator/river/jtsk/trunk \
+           jtsk-trunk
 
      Note also that there are a number of example commands presented
      in this document that use '~' for the user's home directory.
@@ -46,20 +32,16 @@
 
 3. BUILD - the source
 
-     > cd ~/river/jtsk/trunk
+     > cd ~/jtsk-trunk
      > ant clean (optional)
      > ant
      > ant jars
 
-     NOTE: make sure you run the above command from the top-level
-           directory, ~/river/jtsk/trunk, NOT one level lower
-           (~/river/jtsk/trunk/src).
-
 4. INSTALL - the policy provider
 
      > su [must be root to execute the install.policy target]
 
-     # cd ~/river/jtsk/trunk
+     # cd ~/jtsk-trunk
      # ant install.policy
      # ls -al /usr/lib/j2se/jdk1.6.0/jre/lib/ext
 
@@ -71,7 +53,7 @@
 
 5. BUILD - the qa tests
 
-     > cd ~/river/qatests/trunk/source/vob
+     > cd ~/jtsk-trunk/integrationtests
      > make clean (optional)
      > make
      > make jars
@@ -80,7 +62,7 @@
 
      > su [must be root to install this provider]
 
-     # cd ~/river/qatests/trunk/source/vob/qa/lib
+     # cd ~/jtsk-trunk/integrationtests/qa/lib
      # cp mergedpolicyprovider.jar /usr/lib/j2se/jdk1.6.0/jre/lib/ext
      # exit
 
@@ -90,7 +72,7 @@
 
 7. RUNNING - the qa tests
 
-     > cd ~/river/qatests/trunk/source/vob/qa/src
+     > cd ~/jtsk-trunk/integrationtests/qa/src
 
      NOTE: elements of the command line below are broken
            up below for readability
@@ -102,16 +84,16 @@
      com.sun.jini.test.impl.servicediscovery.event.LookupTaskServiceIdMapRace
 
      > java 
-       -cp  <qatestsTrunk>/source/vob/qa/lib/jiniharness.jar
-           :<jtskTrunk>/lib/jsk-platform.jar
-           :<jtskTrunk>/lib/jsk-lib.jar
+       -cp $HOME/jtsk-trunk/integrationtests/qa/lib/jiniharness.jar
+           :$HOME/jtsk-trunk/lib/jsk-platform.jar
+           :$HOME/jtsk-trunk/lib/jsk-lib.jar
        -Djava.security.policy=
-    <qatestsTrunk>/source/vob/qa/harness/policy/qa.policy
+    $HOME/jtsk-trunk/integrationtests/qa/harness/policy/qa.policy
        -Djava.util.logging.config.file=
-    <qatestsTrunk>/source/vob/qa/src/com/sun/jini/test/resources/qa1.logging
+    $HOME/jtsk-trunk/integrationtests/qa/src/com/sun/jini/test/resources/qa1.logging
     com.sun.jini.qa.harness.QARunner
-    <qatestsTrunk>/source/vob/qa/src/com/sun/jini/test/resources/qaHarness.prop
-    -testJar <qatestsTrunk>/source/vob/qa/lib/jinitests.jar
+    $HOME/jtsk-trunk/integrationtests/qa/src/com/sun/jini/test/resources/qaHarness.prop
+    -testJar $HOME/jtsk-trunk/integrationtests/qa/lib/jinitests.jar
     -tests com/sun/jini/test/spec/joinmanager/Register.td,
            com/sun/jini/test/impl/joinmanager/LeaseRenewDurRFE.td,
            com/sun/jini/test/impl/servicediscovery/event/LookupTaskServiceIdMapRace.td
@@ -121,18 +103,16 @@
                  joinmanager categories:
 
      > java 
-       -cp  <qatestsTrunk>/source/vob/qa/lib/jiniharness.jar
-           :<jtskTrunk>/lib/jsk-platform.jar
-           :<jtskTrunk>/lib/jsk-lib.jar
+       -cp $HOME/jtsk-trunk/integrationtests/qa/lib/jiniharness.jar
+           :$HOME/jtsk-trunk/lib/jsk-platform.jar
+           :$HOME/jtsk-trunk/lib/jsk-lib.jar
        -Djava.security.policy=
-    <qatestsTrunk>/source/vob/qa/harness/policy/qa.policy
+    $HOME/jtsk-trunk/integrationtests/qa/harness/policy/qa.policy
        -Djava.util.logging.config.file=
-    <qatestsTrunk>/source/vob/qa/src
-                                     /com/sun/jini/test/resources/qa1.logging
+    $HOME/jtsk-trunk/integrationtests/qa/src/com/sun/jini/test/resources/qa1.logging
     com.sun.jini.qa.harness.QARunner
-    <qatestsTrunk>/source/vob/qa/src
-                                  /com/sun/jini/test/resources/qaHarness.prop
-    -testJar <qatestsTrunk>/source/vob/qa/lib/jinitests.jar
+    $HOME/jtsk-trunk/integrationtests/qa/src/com/sun/jini/test/resources/qaHarness.prop
+    -testJar $HOME/jtsk-trunk/integrationtests/qa/lib/jinitests.jar
     -categories joinmanager 
     -com.sun.jini.qa.harness.serviceMode transient
 
@@ -160,7 +140,7 @@
             optional, but if it is excluded, then only minimal
             default logging output will be displayed. In the
             examples above, the logging file,
-   <qatestsTrunk>/source/vob/qa/src/com/sun/jini/test/resources/qa1.logging
+   $HOME/jtsk-trunk/integrationtests/qa/src/com/sun/jini/test/resources/qa1.logging
             is used to configure logging for both the test
             harness and the tests themselves. Most loggers
             referenced in the qa1.logging configuration file



Mime
View raw message