WPS 2.0 Conformance Test Suite


This executable test suite (ETS) verifies the conformance of the implementation under test (IUT) with respect to the set of relevant specifications depicted in Figure 1. Conformance testing is a kind of "black box" testing that examines the externally visible characteristics or behaviors of the IUT while disregarding any implementation details.

The test suite evaluates compliance of an implementation to:

  • WPS 2.0.2 Interface Standard Corrigendum 2 (OGC 14-065r2)

Support for the following conformance classes is tested:

  • Basic WPS

  • Synchronous WPS

  • Asynchronous WPS

To quality for Compliance certification, a product has to:

  • Pass both the Basic and Synchronous WPS tests, or

  • Pass both the Basic and Asynchronous WPS tests

Test requirements

The documents listed below stipulate requirements that must be satisfied by a conforming implementation.

If any of the following preconditions are not satisfied then all tests in the suite will be marked as skipped.

  1. Precondition. Verify that the server can handle echo process.

Test suite structure

The test suite definition file (testng.xml) is located in the root package, org.opengis.cite.wps20. A conformance class corresponds to a <test> element, each of which includes a set of test classes that contain the actual test methods. The general structure of the test suite is shown in Table 1.

Table 1. Test suite structure
Conformance class Test classes

Conformance Level 1


The Javadoc documentation provides more detailed information about the test methods that constitute the suite.

How to run the tests

The options for running the test suite are summarized below.

As entry point the Landing Page of the WPS 2.0 is expected.

1. Integrated development environment (IDE)

Use a Java IDE such as Eclipse, NetBeans, or IntelliJ. Clone the repository and build the project.

Set the main class to run: org.opengis.cite.wps20.TestNGController

Arguments: The first argument must refer to an XML properties file containing the required test run arguments. If not specified, the default location at $ {user.home}/test-run-props.xml will be used.

You can modify the sample file in src/main/config/test-run-props.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties version="1.0">
	<comment>WPS 2.0 Sample Test Run Arguments</comment>
	<entry key="IUT">https://geoprocessing.demo.52north.org/javaps/service</entry>
	<entry key="ECHO_PROCESS_ID">org.n52.javaps.test.EchoProcess</entry>

The TestNG results file (testng-results.xml) will be written to a subdirectory in ${user.home}/testng/ having a UUID value as its name.

2. Command shell (console)

One of the build artifacts is an "all-in-one" JAR file that includes the test suite and all of its dependencies; this makes it very easy to execute the test suite in a command shell:

java -jar ets-wps20-0.1-SNAPSHOT-aio.jar [-o|--outputDir $TMPDIR] [test-run-props.xml]

3. Docker

This test suite comes with a Dockerfile which can be used to easily setup the OGC test harness with the test suite. Details can be found on Create Docker Image and create and start Docker Container.

4. OGC test harness

Use TEAM Engine, the official OGC test harness. The latest test suite release are usually available at the beta testing facility. You can also build and deploy the test harness yourself and use a local installation.

Using the REST API

Using the REST API of the TEAM Engine requires some run arguments. These ate summarized in Table 2. The Obligation descriptor can have the following values: M (mandatory), O (optional), or C (conditional).

Table 2. Test run arguments
Name Value domain Obligation Description




A URI that refers to the implementation under test or metadata about it. Ampersand ('&') characters must be percent-encoded as '%26'.


A string value.


A string that refers to the echo process id implemented by the service.