commit | 58d9039b6c2db078f1a39f7586dfde2edf705d45 | [log] [tgz] |
---|---|---|
author | Eric Norman <enorman@apache.org> | Tue Jan 19 15:26:58 2021 -0800 |
committer | Eric Norman <enorman@apache.org> | Tue Jan 19 15:26:58 2021 -0800 |
tree | ca1d84ad0c17d31567bc4c0997d6d94df5a3668d | |
parent | aed34f7783352fafc4ad935a8bab9165cc91e7d8 [diff] |
SLING-10074 Add integration tests to verify the various error output formats
This module is part of the Apache Sling project and contains test classes used by the launchpad/testing module.
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 <properties>
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 \ -Dhttp.port=1234 \ -Dtest.host=xyzzy \ -Dhttp.base.path=foo \ -Dwebdav.workspace.path=foo \ -Dlaunchpad.readiness.mediatype=.json:application/json \ -Dtest=**/integrationtest/**/*Test.java
To run or debug tests against the same instance that launchpad/testing
module, see that module's README for how to start the test instance.
The standard -Dmaven.surefire.debug
option can be used to debug the tests themselves.
Some tests might fail if not using a a Sling instance that's not setup by the launchpad/testing module
, as that installs a few additional test bundles.