[
https://issues.apache.org/jira/browse/SLING-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215688#comment-16215688
]
ASF GitHub Bot commented on SLING-7211:
---------------------------------------
rombert closed pull request #4: SLING-7211: fixed broken links.
URL: https://github.com/apache/sling-site/pull/4
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
b/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
index aad08459..18cb6010 100644
---
a/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
+++
b/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
@@ -6,7 +6,7 @@ tags=testing
This is an overview of the Sling bundles that provide support for server-side
JUnit tests.
-The Maven modules below
[`testing/samples`](https://svn.apache.org/repos/asf/sling/trunk/testing/samples)
+The Maven modules below
[`sling-samples/testing`](https://github.com/apache/sling-samples/tree/master/testing)
provide different examples including HTTP-based and server-side teleported
tests in a
bundle module, running against a full Sling instance setup in the same Maven
module.
@@ -158,13 +158,13 @@ The following customizers are currently used in Sling
| `ClientSideTeleporter.testBundleDirectory` | if set the test bundles are
being persisted (before being installed) within the given directory name. If
the directory does not exist, it will be automatically created. Useful for
debugging. Recommended value `${project.build.directory}/test-bundles`. | no |
(-) | 1.0.12 | [SLING-6546](https://issues.apache.org/jira/browse/SLING-6546) |
-The provisioning of an appropriate instance can be done with the
[slingstart-maven-plugin](/documentation/development/slingstart.html). An
example for that is given at
[`testing/samples/module-with-it`](https://svn.apache.org/viewvc/sling/trunk/testing/samples/module-with-it).
Since `slingstart-maven-plugin` 1.5.0 it is possible to bootstrap a Sling
Server from a `model.txt` below `src/test/provisioning` independent of the
packaging (see [SLING-6068](https://issues.apache.org/jira/browse/SLING-6068)).
+The provisioning of an appropriate instance can be done with the
[slingstart-maven-plugin](/documentation/development/slingstart.html). An
example for that is given at
[`sling-samples/testing/module-with-it`](https://github.com/apache/sling-samples/tree/master/testing/module-with-it).
Since `slingstart-maven-plugin` 1.5.0 it is possible to bootstrap a Sling
Server from a `model.txt` below `src/test/provisioning` independent of the
packaging (see [SLING-6068](https://issues.apache.org/jira/browse/SLING-6068)).
#### LaunchpadCustomizer ####
The
*[`LaunchpadCustomizer.java`](https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java)*
only verifies that a Sling instance is ready at a given port and configures
the `ClientSideTeleporter` to deploy to `http://localhost:8080` with the
credentials `admin`:`admin`. `LaunchpadCustomizer` uses the `HttpTestBase`
therefore some parameters are customizable through system properties. There is
no bootstrapping of an instance done here, so this must be done separately!
#### BWIT_TeleporterCustomizer ####
-The
*[`BWIT_TeleporterCustomizer.java`](http://svn.apache.org/viewvc/sling/trunk/testing/samples/bundle-with-it/src/test/java/org/apache/sling/junit/teleporter/customizers/BWIT_TeleporterCustomizer.java)*
relies on `SlingTestBase` to set the server's base url and credentials.
Additionally the test bundle is adjusted so that the API is not included in it
(but rather referenced from another bundle). The bootstrapping of the Sling
instance is tweaked through system properties which are desribed
[here](http://labs.6dglobal.com/blog/2013-06-05/creating-integration-tests-apache-sling/)
and implicitly done by the customizer itself.
+The
*[`BWIT_TeleporterCustomizer.java`](https://github.com/apache/sling-samples/tree/master/testing/bundle-with-it/src/test/java/org/apache/sling/junit/teleporter/customizers/BWIT_TeleporterCustomizer.java)*
relies on `SlingTestBase` to set the server's base url and credentials.
Additionally the test bundle is adjusted so that the API is not included in it
(but rather referenced from another bundle). The bootstrapping of the Sling
instance is tweaked through system properties which are desribed
[here](http://labs.6dglobal.com/blog/2013-06-05/creating-integration-tests-apache-sling/)
and implicitly done by the customizer itself.
Those should give you an overview on what can be done with a customizer and
decide whether you need to write your own one or using the default customizer
is just enough.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Update sample links at "JUnit server-side testing" page
> -------------------------------------------------------
>
> Key: SLING-7211
> URL: https://issues.apache.org/jira/browse/SLING-7211
> Project: Sling
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Oleksandr Tarasenko
> Priority: Minor
> Attachments: doc.patch
>
>
> In the ticket https://issues.apache.org/jira/browse/SLING-7192 some examples
> have been moved and some links on the page
> https://sling.apache.org/documentation/bundles/org-apache-sling-junit-bundles.html
> are broken now.
> Please, see the attached patch with fixes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
