You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by th...@apache.org on 2010/11/09 16:16:26 UTC
svn commit: r1033011 -
/incubator/river/site/trunk/content/building-river.mdtext
Author: thobbs
Date: Tue Nov 9 15:16:22 2010
New Revision: 1033011
URL: http://svn.apache.org/viewvc?rev=1033011&view=rev
Log:
Added details on how to run specific tests/categories and (what I think) is the complete list of test categories.
Modified:
incubator/river/site/trunk/content/building-river.mdtext
Modified: incubator/river/site/trunk/content/building-river.mdtext
URL: http://svn.apache.org/viewvc/incubator/river/site/trunk/content/building-river.mdtext?rev=1033011&r1=1033010&r2=1033011&view=diff
==============================================================================
--- incubator/river/site/trunk/content/building-river.mdtext (original)
+++ incubator/river/site/trunk/content/building-river.mdtext Tue Nov 9 15:16:22 2010
@@ -20,7 +20,21 @@ Notice: Licensed to the Apache Softwa
Before you can start building River a word of warning;
-**The build process does not place nicely if you have spaces in your path names**
+## Warning
+
+The build process does not place nicely if you have spaces in your path names. This includes the install path of the JDK.
+
+This can be circumvented, at least on a Windows/Cygwin by using the first 6 characters of the name with a space in, and postfixing a tilde and the number 1.
+
+For example:
+
+ C:\Program Files
+
+Would become:
+
+ C:\Progra~1
+
+If the first six characters of your path name are not a unique name, for example if you have the two paths "C:\Program Files" and "C:\Program Something Else" then the number after the tilde may well be different. It is suggested that you experiment using the Windows command shell to establish the correct 'tilde plus number' name for your path.
So Windows users please be particular aware. Also, where path separators are specified colons (:) should be used in preference to semi-colons (;) even on Windows.
@@ -45,7 +59,7 @@ This build process runs the (limited) su
### Using the Ant script
-The QA tests can also be run from the Ant script.
+The QA tests can also be run from the Ant script. You must make sure the Ant you are using is using the correct JDK. You can run "ant diagnostics" in the project directory to find out which JVM Ant is using.
Make sure that you have the following in your build.properties file.
@@ -59,7 +73,143 @@ Execute the following:
cd $RIVER_HOME
cd qa.run
-The specific tests and categories of test which are run is set by **doing something which I can't remember**.
+Running the entire QA suite tasks a significant portion of time; currently around the 17 hour mark. It is therefore useful to be able to specify a subset of categories or even specific tests to run. When running the QA tests with Ant, this is done by including the following in the Ant build.properties file.
+
+ # runs a specified category
+ # e.g. run.categories=lookupservice
+ run.categories=name_of_category
+
+ # runs a specified test
+ # e.g. run.tests=com/sun/jini/test/spec/constraint/coreconstraint/PrincipalElementsTest.td
+ run.tests=path/to/test/TestName.td
+
+The td files can be found in;
+
+ $RIVER_HOME/qa/src/**
+
+The test categories are;
+
+ 1. activation
+ 1. activation_spec
+ 1. allgroups
+ 1. basicinvocationdispatcher
+ 1. basicinvocationdispatcher_spec
+ 1. basicinvocationhandler
+ 1. basicinvocationhandler_spec
+ 1. basicobjectendpoint
+ 1. basicobjectendpoint_spec
+ 1. config
+ 1. config_spec
+ 1. constraint
+ 1. constraint_spec
+ 1. coreconstraint
+ 1. coreconstraint_spec
+ 1. discardproblem
+ 1. discoverymanager
+ 1. discoverymanager_impl
+ 1. discoverymanager_spec
+ 1. discoveryproviders
+ 1. discoveryproviders_impl
+ 1. discoveryservice
+ 1. discoveryservice_impl
+ 1. discoveryservice_spec
+ 1. discoveryserviceevent
+ 1. discoveryservicelease
+ 1. end2end
+ 1. end2end_impl
+ 1. eventmailbox
+ 1. eventmailbox_impl
+ 1. eventmailbox_spec
+ 1. export
+ 1. export_spec
+ 1. fiddleradmin
+ 1. fiddlerfiddleradmin
+ 1. fiddlerjoinadmin
+ 1. id
+ 1. id_spec
+ 1. iiop
+ 1. iiop_spec
+ 1. impllocatordiscovery
+ 1. impllookupdiscovery
+ 1. implservicediscovery
+ 1. implservicediscoveryevent
+ 1. io
+ 1. io_spec
+ 1. javaspace
+ 1. javaspace05_conformance
+ 1. javaspace_conformance
+ 1. javaspace_impl
+ 1. javaspace_impl_admin
+ 1. javaspace_impl_api
+ 1. javaspace_impl_javaspace05
+ 1. javaspace_impl_leasing
+ 1. javaspace_impl_matching
+ 1. javaspace_impl_notify
+ 1. javaspace_impl_transaction
+ 1. javaspace_spec
+ 1. jeri
+ 1. jeri_spec
+ 1. joinmanager
+ 1. joinmanager_impl
+ 1. joinmanager_spec
+ 1. jrmp
+ 1. jrmp_spec
+ 1. loader
+ 1. loader_spec
+ 1. locatordiscovery
+ 1. locatordiscovery_impl
+ 1. locatordiscovery_spec
+ 1. lookupdiscovery
+ 1. lookupdiscovery_impl
+ 1. lookupdiscovery_spec
+ 1. lookupservice
+ 1. lookupservice_impl
+ 1. lookupservice_spec
+ 1. policyprovider
+ 1. policyprovider_spec
+ 1. proxytrust
+ 1. proxytrust_spec
+ 1. reliability
+ 1. renewalmanager
+ 1. renewalmanager_spec
+ 1. renewalservice
+ 1. renewalservice_impl
+ 1. renewalservice_spec
+ 1. scalability
+ 1. security
+ 1. security_spec
+ 1. servicediscovery
+ 1. servicediscovery_impl
+ 1. servicediscovery_spec
+ 1. servicediscoverycache
+ 1. servicediscoverydiscovery
+ 1. servicediscoveryevent
+ 1. servicediscoverylookup
+ 1. snapshot
+ 1. spec
+ 1. speclocatordiscovery
+ 1. speclookupdiscovery
+ 1. specservicediscovery
+ 1. specservicediscoverycache
+ 1. specservicediscoverydiscovery
+ 1. specservicediscoveryevent
+ 1. specservicediscoverylookup
+ 1. start
+ 1. start_impl
+ 1. stress
+ 1. test_set00
+ 1. test_set01
+ 1. test_set02
+ 1. test_set03
+ 1. test_set04
+ 1. thread
+ 1. thread_impl
+ 1. txnmanager
+ 1. txnmanager_impl
+ 1. txnmanager_spec
+ 1. url
+ 1. url_spec
+
### Using jtreg directly
@@ -90,6 +240,4 @@ Then to run the jtreg tests execute the
-Djava.security.debug=access,failure \
-Djavatest.maxOutputSize=500000 \
-Djtlib.tmp=./qa/jtreg/JTlib-tmp \
- ./qa/jtreg/
-
-The specific tests and categories of test which are run is set by **doing something which I can't remember**.
\ No newline at end of file
+ ./qa/jtreg/
\ No newline at end of file