SLING-1543 - allow for running single tests from the integration-tests module
git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@950956 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/README.txt b/README.txt
index fedcb78..d8ae4cf 100644
--- a/README.txt
+++ b/README.txt
@@ -1,8 +1,7 @@
Apache Sling Launchpad Testing module
-This module builds a Sling webapp using bundles from the trunk, and
-runs integration tests (that were previously in the launchpad/webapp
-module) on them.
+This module builds a Sling instance using bundles from the trunk, and
+runs integration tests against it, via HTTP.
Getting Started
@@ -28,97 +27,9 @@
See the Subversion documentation for other source control features.
-
-How to run this
----------------
- NOTE: "mvn clean" does not delete the "sling" work directory - make sure to
- delete it manually if you want to start from a clean state.
-
-1) Build all Sling bundles
-
- cd <top of the Sling source code tree>
- mvn clean install
-
-2) Build and run this
-
- cd launchpad/testing
- mvn clean package jetty:run
-
-Once the webapp starts, http://localhost:8888/system/console should display the Felix
-OSGi console.
-
-4) Test node creation and display
-To create a node with curl:
-
- curl -D - -Ftitle=something http://admin:admin@localhost:8888/testing/this
-
-Then, http://admin:admin@localhost:8888/testing/this should display a default HTML
-representation, including the value of the "title" property.
-
-Add a txt or json extension to see other output formats.
-
Integration tests
-----------------
-This module provides a number of integration tests, that run automatically when
-doing a full build, and test Sling via its client HTTP interfaces.
+This module runs number of integration tests provided by the sibling
+integration-tests module.
-These tests can also be run against another instance of Sling, for example to
-test it in another web container than the embedded Jetty that is used during the
-Maven build.
-
-See pom.xml for the parameters that control these integration tests. Here's an
-example of running them against a Sling instance running on host xyzzy, port 1234,
-with the Sling webapp mounted under /foo:
-
- mvn -o -s /dev/null test \
- -Dhttp.port=1234 \
- -Dtest.host=xyzzy \
- -Dhttp.base.path=foo \
- -Dwebdav.workspace.path=foo/dav/default \
- -Dtest=**/integrationtest/**/*Test.java
-
-The -s /dev/null parameter disables all your local Maven settings, to make sure
-they don't interfere (and it's different under Windows). Feel free to remove that
-if you know what you're doing.
-
-To run a single test, other values can be used for the "-Dtest" parameter. To
-leave this launchpad/testing instance running and run individual tests again
-it, for example, use:
-
- mvn launchpad:run
-
-and in another terminal:
-
- mvn test -Dhttp.port=8888 -Dtest=TestClassSelectionNamePattern
-
-This is very useful during development: you can leave a Sling instance
-running, update bundles in it using the mvn autoInstallBundle profile, and run
-specific integration tests quickly from another terminal.
-
-JCR Install Integration tests
------------------------------
-
-This module also contains integration tests for the JCR Install module. These
-tests are disabled by default, since they may not be of general interest. To
-include the JCR Install tests in the integration tests run enable the
-jcrinstall-tests profile such as in
-
- mvn -P jcrinstall-tests integration-test
-
-*** WARNING: the jcrinstall-tests do not work in revision 741168, due to changes
-in the start levels. They can be run according to the scenario below, if you
-change the default bundles start level to 30, after starting the Sling instance
-with mvn jetty:run, from http://localhost:8888/system/console/vmstat. ***
-
-To run the jcrinstall integration tests quickly, without having to start the
-webapp first:
-
-1. Run mvn clean package jetty:run -P jcrinstall-tests in a first console
-
-(1.5 see WARNING above - adjust the default bundles start level)
-
-2. In another console run
-
- mvn test -Pjcrinstall-tests -Dtest=**/integrationtest/jcrinstall/**/*Test.java
-
-
+To run individual tests, see the README.txt in that module.
\ No newline at end of file
