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 2015/09/22 12:13:56 UTC

svn commit: r1704513 - /sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext

Author: bdelacretaz
Date: Tue Sep 22 10:13:52 2015
New Revision: 1704513

URL: http://svn.apache.org/viewvc?rev=1704513&view=rev
Log:
Tweak JUnit server-side docs

Modified:
    sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.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=1704513&r1=1704512&r2=1704513&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 Sep 22 10:13:52 2015
@@ -23,7 +23,7 @@ The `TeleporterRule` supplied by this bu
 all the mechanics of creating the test bundle, adding the above header, installing it etc.
 
 Using this rule the server-side tests can be mixed with other tests in the source code if that's convenient, it just
-requires the `junit.core`and `junit.teleporter` modules described on this page to create such tests. 
+requires the `junit.core` and `junit.teleporter` modules described on this page to create such tests. 
 
 Here's a basic example of a server-side test that accesses OSGi services:
 
@@ -68,7 +68,7 @@ and combining them using JUnit's `RuleCh
 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
-described above. Or use the `TeleporterRule`and set a breakpoint in the tests execution, when the test bundle in
+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.
 
 To list the available tests, open `/system/sling/junit/` in your browser. The servlet shows available tests and allows 
@@ -81,8 +81,10 @@ Adding a path allows you to select a spe
  `/system/sling/junit/.json` for example.
 
 ## org.apache.sling.junit.teleporter: client-side TeleporterRule support
-This module provides the `ClientSideTeleporter` which the `TeleporterRule` uses to teleport the tests
-to the server side. It is not a bundle, as it's used on the client only, as a dependency when running the tests.
+This module provides the `ClientSideTeleporter` which the `TeleporterRule` uses to package the server-side tests
+in bundles that's installed temporarily on the test server. 
+
+This module is not a bundle, as it's used on the client only, as a dependency when running the tests.
 
 A `TeleporterRule.Customizer` is used to setup the `ClientSideTeleporter`. That customizer is instantiated dynamically
 based on a String passed to the `TeleporterRule` creation code.