You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bd...@apache.org on 2009/02/05 17:37:43 UTC

svn commit: r741171 - /incubator/sling/trunk/launchpad/testing/README.txt

Author: bdelacretaz
Date: Thu Feb  5 16:37:43 2009
New Revision: 741171

URL: http://svn.apache.org/viewvc?rev=741171&view=rev
Log:
SLING-738 - additional info on jcrinstall integration tests

Modified:
    incubator/sling/trunk/launchpad/testing/README.txt

Modified: incubator/sling/trunk/launchpad/testing/README.txt
URL: http://svn.apache.org/viewvc/incubator/sling/trunk/launchpad/testing/README.txt?rev=741171&r1=741170&r2=741171&view=diff
==============================================================================
--- incubator/sling/trunk/launchpad/testing/README.txt (original)
+++ incubator/sling/trunk/launchpad/testing/README.txt Thu Feb  5 16:37:43 2009
@@ -103,3 +103,21 @@
 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
+  
+