svn commit: r1735142 - in /sling/site/trunk/content/documentation: bundles/org-apache-sling-junit-bundles.mdtext development/sling-testing-tools.mdtext

[bd...@apache.org]

Author: bdelacretaz
Date: Tue Mar 15 17:02:01 2016
New Revision: 1735142

URL: http://svn.apache.org/viewvc?rev=1735142&view=rev
Log:
SLING-5611 - remove references to obsolete sample bundles

Modified:
    sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext
    sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext

Modified: sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext?rev=1735142&r1=1735141&r2=1735142&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext Tue Mar 15 17:02:01 2016
@@ -87,9 +87,8 @@ number of tests in our `launchpad/integr
 and combining them using JUnit's `RuleChain`, should help work around such limitations if they arise.
 
 ### More details on the JUnitServlet
-To try the JUnitServlet interactively, you can install the 
-[org.apache.sling.testing.samples.sampletests](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/sample-tests) 
-bundle, or any other bundle that contains tests and a `Sling-Test-Regexp` bundle header that points to them, as
+To try the JUnitServlet interactively, you can install a
+bundle that contains tests and a `Sling-Test-Regexp` bundle header that points to them, as
 described above. Or use the `TeleporterRule` and set a breakpoint in the tests execution, when the test bundle in
 installed and listed by the test servlet.
 

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=1735142&r1=1735141&r2=1735142&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext (original)
+++ sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext Tue Mar 15 17:02:01 2016
@@ -36,9 +36,9 @@ Note that the JUnitServlet does not requ
 For tighter integration with Sling, the alternate `SlingJUnitServlet` is registered with the `sling/junit/testing` resource type and `.junit` selector, if the bundle is running in a Sling system. Using this servlet instead of the plain JUnitServlet also allows Sling authentication to be used for running the tests, and the standard Sling request processing is used, including servlet filters for example.
 </div>
 
-To try the JUnitServlet interactively, install the [org.apache.sling.testing.samples.sampletests](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/sample-tests) bundle.
+To try the JUnitServlet interactively, install a bundle that contains tests registered via the `Sling-Test-Regexp=.*Test` bundle header. 
 
-This bundle contains a number of test classes, which are registered with the `org.apache.sling.junit.core` services by way of the `Sling-Test-Regexp=.*Test` bundle header, defined in the bundle's `pom.xml`. The JUnit core services use this regular expression to select which classes of the test bundle should be executed as JUnit tests.
+The JUnit core services use this regular expression to select which classes of the test bundle should be executed as JUnit tests.
 
 To list the available tests, open http://localhost:8080/system/sling/junit/ . The servlet shows available tests, and allows you to execute them via a POST request.
 
@@ -47,7 +47,7 @@ Adding a path allows you to select a spe
 To supply tests from your own bundles, simply export the tests classes and add the `Sling-Test-Regexp` header to the bundle so that the Sling JUnit core services register them as tests.
 
 ### Injection of OSGi services
-The `@TestReference` annotation is used to inject OSGi services in tests that are executed server side.The `BundleContext` can also be injected in this way, see the [OsgiAwareTest](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/sample-tests/src/main/java/org/apache/sling/testing/samples/sampletests/OsgiAwareTest.java) for an example.
+The `@TestReference` annotation is used to inject OSGi services in tests that are executed server side.The `BundleContext` can also be injected in this way.
 
 ## Curl examples
 Here's an example executing a few tests using curl: