svn commit: r1464499 - /sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext

[bd...@apache.org]

Author: bdelacretaz
Date: Thu Apr  4 12:27:09 2013
New Revision: 1464499

URL: http://svn.apache.org/r1464499
Log:
fix formatting

Modified:
    sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext

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=1464499&r1=1464498&r2=1464499&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext (original)
+++ sling/site/trunk/content/documentation/development/sling-testing-tools.mdtext Thu Apr  4 12:27:09 2013
@@ -17,13 +17,13 @@ See also [Testing Sling-based applicatio
 # Server-side JUnit tests contributed by bundles
 The services provided by the [org.apache.sling.junit.core]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/testing/junit/core.path }}) bundle allow bundles to register JUnit tests, which are executed server-side by the JUnitServlet registered by default at `/system/sling/junit`. This bundle is not dependent on Sling, it should work in other OSGi environments.
 
-{warning:title=JUnit servlet security}
+<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.
-{warning}
+</div>
 
-{note:title=SlingJUnitServlet}
+<div class="note">
 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.
-{note}
+</div>
 
 To try the JUnitServlet interactively, install the [org.apache.sling.testing.samples.sampletests]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/testing/samples/sample-tests.path }}) bundle.
 
@@ -41,7 +41,6 @@ The `@TestReference` annotation is used 
 ## Curl examples
 Here's an example executing a few tests using curl:
 
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>Running tests with curl</B></DIV><DIV class="codeContent panelContent">
     $ curl -X POST http://localhost:8080/system/sling/junit/org.apache.sling.testing.samples.sampletests.JUnit.json
     [{
         "INFO_TYPE": "test",
@@ -57,10 +56,7 @@ Here's an example executing a few tests 
 
 
 And another example with a test that fails:
-<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>Failing tests with curl</B></DIV><DIV class="codeContent panelContent">
     $ curl -X POST http://localhost:8080/system/sling/junit/org.apache.sling.testing.samples.failingtests.JUnit4FailingTest.json
-    [continuous integration|SLINGxSITE:Project Information]
-
 
 # Scriptable server-side tests
 If the [org.apache.sling.junit.scriptable]({{ refs.http://svn.apache.org/repos/asf/sling/trunk/testing/junit/scriptable.path }}) bundle is active in a Sling system, (in addition to the `org.apache.sling.junit.core` bundle), scriptable tests can be executed by the `JUnitServlet` according to the following rules: