You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by si...@apache.org on 2011/01/07 11:24:35 UTC
svn commit: r1056242 -
/incubator/river/site/trunk/content/river/building-river.mdtext
Author: sijskes
Date: Fri Jan 7 10:24:34 2011
New Revision: 1056242
URL: http://svn.apache.org/viewvc?rev=1056242&view=rev
Log:
CMS commit to river by sijskes
Modified:
incubator/river/site/trunk/content/river/building-river.mdtext
Modified: incubator/river/site/trunk/content/river/building-river.mdtext
URL: http://svn.apache.org/viewvc/incubator/river/site/trunk/content/river/building-river.mdtext?rev=1056242&r1=1056241&r2=1056242&view=diff
==============================================================================
--- incubator/river/site/trunk/content/river/building-river.mdtext (original)
+++ incubator/river/site/trunk/content/river/building-river.mdtext Fri Jan 7 10:24:34 2011
@@ -74,17 +74,17 @@ That should everything that Eclipse need
### NetBeans
*TODO*
-## Testing River
+# Testing River
This build process runs the (limited) suite of unit tests that comes with River. River is tested predominantly by using [jtreg](http://openjdk.java.net/jtreg/) and the QA test suite.
-### The JUnit tests
+## The JUnit tests
The JUnit tests can be found in `$RIVER_HOME/test/src` you must also add the JARs found in `$RIVER_HOME/test/lib` onto the classpath for your tests.
It's easiest to run these tests from your IDE. In Eclipse, for example, once `$RIVER_HOME/test/src` is set at the test source directory, right-clicking the project and hitting "Run as JUnit test" is all that is required.
-### The QA Test Suite
+## The QA Test Suite
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 which you will need to create in `$RIVER_HOME`.
@@ -101,10 +101,10 @@ Execute the following:
cd $RIVER_HOME
cd qa.run
-#### Running just a few tests
+### Running just a few tests
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.
-##### By settings in the properties file
+#### By settings in the properties file
When running the QA tests with Ant, this is done by including the following in the Ant build.properties file.
# runs a specified category
@@ -115,17 +115,17 @@ When running the QA tests with Ant, this
# e.g. run.tests=com/sun/jini/test/spec/constraint/coreconstraint/PrincipalElementsTest.td
run.tests=path/to/test/TestName.td
-##### By specifying on the commandline
+#### By specifying on the commandline
From the qa directory:
ant -Drun.tests=com/sun/jini/test/spec/constraint/coreconstraint/PrincipalElementsTest.td run-tests
Existing QA tests can be found in the following path; `$RIVER_HOME/qa/src/com/sun/jini/test/**"`
-#### Categories
+### Categories
You can find the test categories on [Test categories](testing-categories.html)
-### JTREG tests
+## JTREG tests
You must first download and install jtreg following the instructions on their site.
@@ -145,11 +145,11 @@ The JTREG tests can then be run by execu
JTREG will create the directory `$RIVER_HOME/qa/jtreg/JTreport` which contains a report of the test run.
-#### Running specific JTREG tests
+### Running specific JTREG tests
_todo_
-#### Known Problems
+### Known Problems
There are the following known problems with the jtreg tests:
1. Running the tests in a Windows/Cygwin environment is not 100% working yet