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 11:58:37 UTC

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

Author: bdelacretaz
Date: Tue Sep 22 09:58:34 2015
New Revision: 1704503

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

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=1704503&r1=1704502&r2=1704503&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 09:58:34 2015
@@ -9,7 +9,7 @@ To make tests available to that servlet,
 with a `Sling-Test-Regexp` bundle header that defines a regular expression that matches
 the test class names, like for example:
 
-    Sling-Test-Regexp=`com.example.*ServerSideTest
+    Sling-Test-Regexp=com.example.*ServerSideTest
 
 <div class="warning">
 Note that the JUnitServlet does not require authentication, so it would allow any client to run tests. The servlet can be disabled by configuration if needed, but in general the `/system` path should not be accessible to website visitors anyway.

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=1704503&r1=1704502&r2=1704503&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext (original)
+++ sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext Tue Sep 22 09:58:34 2015
@@ -2,9 +2,11 @@ Title: Sling Testing Tools
 
 <div class="warning">
 While this information is still valid, we recommend using the tools and techniques described
-in the newer [Junit Server-Side Tests Support]({{ refs.org-apache-sling-junit-bundles.path }}) page instead. 
+in the newer "Junit Server-Side Tests Support" page instead, see link below. 
 </div>
 
+As mentioned above, this is now replaced by the [Junit Server-Side Tests Support]({{ refs.org-apache-sling-junit-bundles.path }}) page. 
+
 Sling provides a number of testing tools to support the following use cases:
 
 * Run JUnit tests contributed by OSGi bundles in an OSGi system. This does not require Sling and should work in other OSGi  environments.