Replace deegree-compliance-tests by official and final OGC ETS

[tfr42]

Currently the OGC CITE Tests in deegree-tests/deegree-compliance-tests for

• WCS 1.0.0
• WFS 1.0.0, 1.1.0
• WMS 1.1.1, 1.3.0 are based on quite old forks of the related OGC ETS.

Prefered setup is based on most recent release version of the official OGC CITE ETS. Including ETS for:

• WFS 2.0
• WMTS 1.0
• CSW 2.0.2
• WPS 1.0

[tfr42]

CLI available in OGC TEAM engine: https://github.com/opengeospatial/cite/wiki/Conformance-Testing-with-TestNG-Part-2#12-2-command-shell-console All-in-one (AIO) JAR available for WFS 2.0 ETS from https://repo1.maven.org/maven2/org/opengis/cite/ets-wfs20/1.32/

[tfr42]

The OSGeo Foundation has started an OGC Certification Service to provide a public demonstration instance used for the OGC TEAM Engine to be executed against. See the wiki https://wiki.osgeo.org/wiki/OGC_Certification_Services for more information.

[dstenger]

Disadvantage when decoupling the CITE integration tests from Maven build: Tests cannot be executed against feature branches used for pull requests.

Possible workflows (decoupled from Maven build):

• Workflow 1: Usage of Docker (independent from OGC infrastructure).

  • 1. Create and start Docker Container with latest deegree artifact.
    • deegree CITE workspace is integrated into the container.
  • 2. Create and start Docker Container of OGC test suites.
    • These are available via Docker Hub (https://hub.docker.com/u/ogccite).
  • 3. Execute SoapUI tests which use the REST interface of the OGC test suites to test the deegree endpoints.
    • SoapUI parses the responses and applies assertions.
    • SoapUI tests can be started headless either via Maven or CLI.
    • Alternatively, Java can be used instead of SoapUI.

• Workflow 2: No usage of Docker (depends on OGC infrastructure).

  • 1. Start the latest deegree artifact with Java (e.g. via using Maven plus plugin).
    • deegree CITE workspace can be accessed by deegree instance.
  • 2. Execute SoapUI tests which use the REST interface of the OGC infrastructure (https://cite.opengeospatial.org/teamengine/) to test the deegree endpoints.
    • See sub bullet points of step 3 of workflow 1.

• Workflow 3: No usage of Docker (independent from OGC infrastructure).

  • 1. Start the latest deegree artifact with Java (e.g. via using Maven plus plugin).
    • deegree CITE workspace can be accessed by deegree instance.
  • 2. Use the CLIs of the OGC test suites to test the deegree endpoints.
    • Java is used for parsing and evaluation of the results.
    • There are two mechanisms: All-in-one (AIO) JARs (only new test suites) and TEAM Engine via command line (setup quite complex).

All workflows can be realized via Jenkinsfile(s).

[dstenger]

Currently the OGC CITE Tests in deegree-tests/deegree-compliance-tests for

• WCS 1.0.0

OGC CITE status: Production Repo: https://github.com/opengeospatial/ets-wcs11/

• WFS 1.0.0, 1.1.0

OGC CITE status: Production, Production Repo: https://github.com/opengeospatial/ets-wfs10, https://github.com/opengeospatial/ets-wfs11

• WMS 1.1.1, 1.3.0

OGC CITE status: Production, Production Repo: https://github.com/opengeospatial/ets-wms11, https://github.com/opengeospatial/ets-wms13

are based on quite old forks of the related OGC ETS.

Prefered setup is based on most recent release version of the official OGC CITE ETS. Including ETS for:

• WFS 2.0

OGC CITE status: Production Repo: https://github.com/opengeospatial/ets-wfs20

• WMTS 1.0

OGC CITE status: Production Repo: https://github.com/opengeospatial/ets-wmts10

• CSW 2.0.2

OGC CITE status: Production Repo: https://github.com/opengeospatial/ets-csw202

• WPS 1.0

OGC CITE status: Beta (development is currently ongoing) Repo: https://github.com/opengeospatial/ets-wps10

[tfr42]

OGC TEAM Engine is available via docker hub, see #1276

[dstenger]

Both OGC CITE test environments (https://cite.ogc.org/teamengine/ and https://cite.ogc.org/te2/) are now also available via Docker Hub:

• https://hub.docker.com/r/ogccite/teamengine-production
• https://hub.docker.com/r/ogccite/teamengine-beta

This makes it easy to setup the environment on a target machine to use it for automated integration tests (via REST interface).