This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 90e3fd0 Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/59/
90e3fd0 is described below
commit 90e3fd09d9be47c991e23b1010a3d6a45eed2bb4
Author: jenkins <[email protected]>
AuthorDate: Thu Oct 22 09:04:14 2020 +0000
Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/59/
---
documentation/bundles/org-apache-sling-junit-bundles.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/bundles/org-apache-sling-junit-bundles.html
b/documentation/bundles/org-apache-sling-junit-bundles.html
index 0d79050..0ead7ce 100644
--- a/documentation/bundles/org-apache-sling-junit-bundles.html
+++ b/documentation/bundles/org-apache-sling-junit-bundles.html
@@ -140,7 +140,7 @@ For tighter integration with Sling, the alternate
`SlingJUnitServlet` is registe
<blockquote>
<p><strong>JUnit 5 = <em>JUnit Platform</em> + <em>JUnit Jupiter</em> +
<em>JUnit Vintage</em></strong></p>
</blockquote>
-<p>Source: <a
href="https://junit.org/junit5/docs/current/user-guide/#overview-what-is-junit-5";>JUnit
5 User Guide - What is JUnit 5?</a></p>
+<p><em>Source:</em> <a
href="https://junit.org/junit5/docs/current/user-guide/#overview-what-is-junit-5";
target="_blank">JUnit 5 User Guide - What is JUnit 5?</a></p>
<p><a href="#junit-platform">JUnit Platform</a>: a generic platform for
launching testing frameworks that defines the <code>TestEngine</code> API, an
extension point for hooking in arbitrary ways of describing tests.</p>
<p><a href="#bundles-for-the-junit-jupiter-engine-junit-5">JUnit Jupiter</a>:
a <code>TestEngine</code> that can run Jupiter based tests on the platform.
I.e. it runs tests that are coloquially referred to as JUnit 5 tests.</p>
<p><a href="#bundles-for-the-junit-vintage-engine-junit-4">JUnit Vintage</a>:
a <code>TestEngine</code> that can run JUnit 3 and JUnit 4 based tests on the
platform.</p>
@@ -153,7 +153,7 @@ For tighter integration with Sling, the alternate
`SlingJUnitServlet` is registe
<li>org.junit.platform:junit-platform-launcher</li>
</ul>
<div class="note">
-Note: `junit-platform-commons` version 1.7.0 cannot be deployed using Sling's
OSGi Installer, due to [junit5 issue
#2438](https://github.com/junit-team/junit5/issues/2438). Other JUnit5 bundles
_may_ be affected by the same issue.
+Note: `junit-platform-commons` version 1.7.0 cannot be deployed using Sling's
OSGi Installer, due to <a
href="https://github.com/junit-team/junit5/issues/2438"; target="_blank">junit5
issue #2438</a>. Other JUnit5 bundles _may_ be affected by the same issue.
</div>
<p>However, in order to run tests at least one implementation of
<code>org.junit.platform.engine.TestEngine</code> needs to be available. Both
<a href="#bundles-for-the-junit-jupiter-engine-junit-5">JUnit Jupiter</a> and
<a href="#bundles-for-the-junit-vintage-engine-junit-4">JUnit Vintage</a>
provide a test engine, so at least one of the two needs to be deployed.</p>
<p>Custom or other other 3rd party <code>TestEngine</code> implementations
should be able to hook in transparently, provided they are advertised using
Java's <code>ServiceLoader</code> mechanism. Apache Sling Junit Core takes care
of detecting test engines in other installed bundles and automatically makes
them available for test execution.</p>
@@ -173,7 +173,7 @@ Note: `junit-platform-commons` version 1.7.0 cannot be
deployed using Sling's OS
<li>org.junit.vintage:junit-vintage-engine</li>
</ul>
<div class="note">
-Note: the JUnit Vintage engine is only required if JUnit 4 and JUnit 5 tests
should be executed side-by-side. For plain JUnit 4 support _only_ the Apache
Sling JUnit Core bundle needs to be installed. For plain Jupiter (or JUnit 5)
tests, see [JUnit Jupiter](#bundles-for-the-junit-jupiter-engine-junit-5).
+Note: the JUnit Vintage engine is only required if JUnit 4 and JUnit 5 tests
should be executed side-by-side. For plain JUnit 4 support _only_ the Apache
Sling JUnit Core bundle needs to be installed. For plain Jupiter (or JUnit 5)
tests, see <a href="#bundles-for-the-junit-jupiter-engine-junit-5">JUnit
Jupiter</a>.
</div>
<h3><a href="#the-teleporterrule" id="the-teleporterrule">The
TeleporterRule</a></h3>
<p>The <code>TeleporterRule</code> supplied by this bundle (since V1.0.12)
makes it easy to write such tests, as it takes care of all the mechanics of</p>
@@ -304,7 +304,7 @@ TEST_PASSED
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Julian
Sedding</span> on <span class="comment">Wed Oct 21 12:05:13 2020 +0200</span>
+ Last modified by <span class="author">Julian
Sedding</span> on <span class="comment">Thu Oct 22 10:58:34 2020 +0200</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo,
and the Apache Sling project logo are trademarks of The Apache Software
Foundation. All other marks mentioned may be trademarks or registered
trademarks of their respective owners.
</p><p>
