commit | 184b10bb6b7bbd1c675b34c83c83a93f3d4e25fe | [log] [tgz] |
---|---|---|
author | Bertrand Delacretaz <bdelacretaz@apache.org> | Fri Jul 30 10:44:50 2021 +0200 |
committer | Bertrand Delacretaz <bdelacretaz@apache.org> | Fri Jul 30 10:44:50 2021 +0200 |
tree | c94ff5bdce0f84db16c0a330fef78898593e38a0 | |
parent | 52c3644cc2b9b6bbfb50a74c21980fd6a155675a [diff] |
SLING-10676 - remove SECURITY.md which is not needed
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.