Author: buildbot
Date: Tue Sep 22 14:17:15 2015
New Revision: 966358
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 22 14:17:15 2015
@@ -1 +1 @@
-1704544
+1704637
Modified:
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
Tue Sep 22 14:17:15 2015
@@ -130,6 +130,7 @@ the test class names, like for example:<
</pre></div>
+<h3 id="the-teleporterrule">The TeleporterRule<a class="headerlink"
href="#the-teleporterrule" title="Permanent link">¶</a></h3>
<p>The <code>TeleporterRule</code> 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.</p>
<p>Using this rule the server-side tests can be mixed with other tests in the
source code if that's convenient, it just
@@ -244,7 +245,7 @@ same request again. </p>
but using the newer <code>TeleporterRule</code> described above is much
simpler. As a result, this bundle
should only be needed for existing tests that were written using its
mechanisms. </p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1704513 by bdelacretaz on Tue, 22 Sep 2015 10:13:52 +0000
+ Rev. 1704637 by bdelacretaz on Tue, 22 Sep 2015 14:16:57 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
