https://github.com/opengeospatial/ets-wps20
https://github.com/opengeospatial/ets-wps20
Last synced: 6 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/opengeospatial/ets-wps20
- Owner: opengeospatial
- License: other
- Created: 2021-03-16T15:57:38.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2025-01-23T13:59:49.000Z (over 1 year ago)
- Last Synced: 2025-02-25T09:42:47.408Z (over 1 year ago)
- Language: Java
- Size: 1020 KB
- Stars: 2
- Watchers: 13
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.adoc
- License: LICENSE.txt
Awesome Lists containing this project
README
= Web Processing Service 2.0 Executable Test Suite
== Scope
This executable test suite is for version 2.0 of the https://www.ogc.org/standards/wps[OGC Web Processing Service (WPS)] standard.
Visit the http://opengeospatial.github.io/ets-wps20/[project documentation website]
for more information, including the API documentation.
== How to build the test suite
The test suite is built using https://maven.apache.org/[Apache Maven v3].
Step 1. First clone the repo.
`git clone https://github.com/opengeospatial/ets-wps20.git`
Step 2. Then navigate into the local repo.
`cd ets-wps20`
Step 3. Now clean the project.
`mvn clean`
Step 4. Now build the project.
`mvn package`
NOTE: On some operating systems, when building the ETS under Java 11+ for the first time, it may be necessary to run `mvn package` twice.
NOTE: Running `mvn package` will automatically update the jar file `ets-wps20-x.x-SNAPSHOT.jar` in the `/ets-wps20/docker/teamengine/WEB-INF/lib`. To disable this function, modify `maven-antrun-plugin` in the pom.xml file.
== How to run the test suite
The options for running the suite are summarized in
include::src/site/asciidoc/how-to-run-the-tests.adoc[]
== How to contribute
If you would like to get involved, you can:
* https://github.com/opengeospatial/ets-wps20/issues[Report an issue] such as a defect or
an enhancement request
* Help to resolve an https://github.com/opengeospatial/ets-wps20/issues?q=is%3Aopen[open issue]
* Fix a bug: Fork the repository, apply the fix, and create a pull request
* Add new tests: Fork the repository, implement and verify the tests on a new topic branch,
and create a pull request (don't forget to periodically rebase long-lived branches so
there are no extraneous conflicts)