Skip to content

Commit

Permalink
SLING-7935 - Move launchpad-testing module into the main starter repo…
Browse files Browse the repository at this point in the history
…sitory

Remove references to the launchpad-testing module, now that the tests
are executed in the Sling Starter.
  • Loading branch information
rombert committed May 11, 2022
1 parent e7b3fdf commit f26204d
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 8 deletions.
12 changes: 5 additions & 7 deletions src/main/jbake/content/contributing.md
Expand Up @@ -73,15 +73,13 @@ In case your changes are more far-reaching and the module you are contributing t
[Sling Starter](https://github.com/apache/sling-org-apache-sling-starter), it is a good idea to
also run the Sling Starter integration tests. This can be achieved by doing the following:
* Check out the [Sling Starter](https://github.com/apache/sling-org-apache-sling-starter) and
[Sling Starter Integration Tests](https://github.com/apache/sling-org-apache-sling-launchpad-testing)
projects. This step can be skipped if you have followed the steps to checkout all Sling repositories
* Check out the [Sling Starter](https://github.com/apache/sling-org-apache-sling-starter) project.
This step can be skipped if you have followed the steps to checkout all Sling repositories
as documented at [Getting and Building Sling](/documentation/development/getting-and-building-sling.html#getting-the-sling-source)
* Use the latest version of the bundle(s) you changed in the Sling Starter. Running `git grep ${ARTIFACT_ID}`
will indicate the potential places where you need to make changes
* Run `mvn clean install` in the Sling Starter checkout. This runs a set of Smoke tests and allows the
integration tests to use the version of the starter that you just built
* Run `mvn clean install` in the Sling Starter Integration Tests checkout
* Run `mvn clean verify` in the Sling Starter checkout. This runs the full set of integration tests that
we use for Sling modules.
Additionally, and PR you submit will eventually be built by Jenkins, with additional validations on top
of the plain Maven build.
2 changes: 1 addition & 1 deletion src/main/jbake/content/documentation/development.md
Expand Up @@ -61,4 +61,4 @@ Last but not least, here is some more information on how we ourselves are workin
* [Deprecating Sling Modules](/documentation/development/deprecating-sling-modules.html)
* [Maven Usage](/documentation/development/maven-usage.html)
* [Build Setup](/project-information.html#continuous-integration)
* To run our integration tests suite see the [launchpad/testing module README](https://github.com/apache/sling-org-apache-sling-launchpad-testing/blob/master/README.md) and the [launchpad/integration-tests README](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/README.md) for how to run individual integration tests. We use the [sling-IT](https://issues.apache.org/jira/issues/?jql=labels%20%3D%20sling-IT) label in JIRA for known issues with our integration tests.
* To run our integration tests suite see the [Sling Starter module README](https://github.com/apache/sling-org-apache-sling-starter/blob/master/README.md) and the [launchpad/integration-tests README](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/README.md) for how to run individual integration tests. We use the [sling-IT](https://issues.apache.org/jira/issues/?jql=labels%20%3D%20sling-IT) label in JIRA for known issues with our integration tests.

0 comments on commit f26204d

Please sign in to comment.