svn commit: r1641357 - /sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext

[bd...@apache.org]

Author: bdelacretaz
Date: Mon Nov 24 10:34:00 2014
New Revision: 1641357

URL: http://svn.apache.org/r1641357
Log:
Testing tools, point to required bundles

Modified:
    sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext

Modified: sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext?rev=1641357&r1=1641356&r2=1641357&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext (original)
+++ sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext Mon Nov 24 10:34:00 2014
@@ -14,6 +14,10 @@ The main Sling integration tests at [lau
 
 See also [Testing Sling-based applications]({{ refs.testing-sling-based-applications.path }}) which discusses testing in general.
 
+## Required bundles
+These tools require a number of bundles on top of the standard Sling launchpad. See the [sample tests pom.xml](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/integration-tests/pom.xml)
+for an up-to-date list. Look for `sling.additional.bundle.*` entries in that pom for the bundle artifact IDs, and see the `dependencies` section for their version numbers.
+
 # Server-side JUnit tests contributed by bundles
 The services provided by the [org.apache.sling.junit.core](http://svn.apache.org/repos/asf/sling/trunk/testing/junit/core) bundle allow bundles to register JUnit tests, which are executed server-side by the JUnitServlet registered by default at `/system/sling/junit`. This bundle is not dependent on Sling, it should work in other OSGi environments.