Author: bdelacretaz
Date: Tue Sep 22 14:16:57 2015
New Revision: 1704637
URL: http://svn.apache.org/viewvc?rev=1704637&view=rev
Log:
Add subtitle
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=1704637&r1=1704636&r2=1704637&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 14:16:57 2015
@@ -19,6 +19,8 @@ the test class names, like for example:
Sling-Test-Regexp=com.example.*ServerSideTest
+### The TeleporterRule
+
The `TeleporterRule` supplied by this bundle makes it easy to write such
tests, as it takes care of
all the mechanics of creating the test bundle, adding the above header,
installing it etc.
@@ -146,4 +148,4 @@ same request again.
The `org.apache.sling.junit.remote` bundle provides utilities to run
server-side JUnit tests,
but using the newer `TeleporterRule` described above is much simpler. As a
result, this bundle
-should only be needed for existing tests that were written using its
mechanisms.
\ No newline at end of file
+should only be needed for existing tests that were written using its
mechanisms.
