Apache Sling Launchpad Integration Tests

Clone this repo:
  1. 9b271bf SLING-7935 - Consolidate all 'launchpad-testing' modules into a single git repository by Robert Munteanu · 4 months ago master
  2. 24ee3ae [maven-release-plugin] prepare for next development iteration by Robert Munteanu · 4 months ago
  3. 8549fec [maven-release-plugin] prepare release org.apache.sling.launchpad.integration-tests-1.0.10 by Robert Munteanu · 4 months ago org.apache.sling.launchpad.integration-tests-1.0.10
  4. bf18a6c Revert "SLING-7935 - Consolidate all 'launchpad-testing' modules into a single git repository" by Robert Munteanu · 4 months ago
  5. 5023d06 SLING-8343 fix failing integration test related to recent healthcheck changes by Eric Norman · 6 months ago

Build Status Maven Central JavaDocs License launchpad

Apache Sling Launchpad Integration Tests

This module is part of the Apache Sling project.

This module contains test classes used by the launchpad/testing module, separated in their own jar to be reusable.

To run a single test or a specific set of tests against a running Sling instance, use for example:

mvn test -Dtest=UploadFileTest -Dhttp.port=1234

Where UploadFileTest is the test to run. Wildcards are allowed, and test classes are found in the src/main folder (not a typo - that's not src/test as we want to pack the tests in the jar file that we build).

See the section in pom.xml for additional parameters that the tests use.

Here's another example, running the tests against a Sling instance running on host xyzzy, port 1234, with the Sling main servlet mounted under /foo:

mvn -o -s /dev/null test
-Dlaunchpad.readiness.mediatype=.json:application/json \ -Dtest=/integrationtest//*Test.java

To run the tests against the same instance that is used in the full build, start an instance by running

mvn clean install -Dlaunchpad.keep.running=true -Dhttp.port=8080 -Ddebug=true

in the launchpad/testing folder (-Ddebug is optional).

And use the same -Dhttp.port option to run tests here.

The standard -Dmaven.surefire.debug option can be used to debug the tests themselves. Have a look at the README.txt in the launchpad.testing module on how to debug the server-side Sling code.

If using a Sling instance that's not setup by the launchpad/testing module, note that for all tests to pass that instance needs the org.apache.sling.launchpad.test-services bundle to be active and the war file of the launchpad/test-services-war project to be be copied to the sling/startup/0 folder before starting Sling.