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 2008/12/03 14:56:27 UTC

svn commit: r722887 - /incubator/sling/trunk/extensions/jcrinstall/testing/README.txt

Author: bdelacretaz
Date: Wed Dec  3 05:56:26 2008
New Revision: 722887

URL: http://svn.apache.org/viewvc?rev=722887&view=rev
Log:
SLING-734 - document test parameters

Modified:
    incubator/sling/trunk/extensions/jcrinstall/testing/README.txt

Modified: incubator/sling/trunk/extensions/jcrinstall/testing/README.txt
URL: http://svn.apache.org/viewvc/incubator/sling/trunk/extensions/jcrinstall/testing/README.txt?rev=722887&r1=722886&r2=722887&view=diff
==============================================================================
--- incubator/sling/trunk/extensions/jcrinstall/testing/README.txt (original)
+++ incubator/sling/trunk/extensions/jcrinstall/testing/README.txt Wed Dec  3 05:56:26 2008
@@ -66,4 +66,16 @@
 
 This is very useful during development: you can leave a Sling webapp instance
 running, update bundles in it using the mvn autoInstallBundle profile, and run
-specific integration tests quickly from another terminal.
\ No newline at end of file
+specific integration tests quickly from another terminal.
+
+Test parameters
+---------------
+The following values can be used to test with various quantities of test bundles.
+Default values are defined in pom.xml.
+
+  -Dsling.test.scale.factor=1
+  -Dsling.test.bundles.wait.seconds=20
+  
+ Increasing the scale factor causes the tests to run with corresponding more bundles,
+ and the wait time must be adjusted accordingly, to leave enough time for the framework
+ to start the bundles installed during tests.