This test suite verifies that a Web Map Service (WMS) component meets the requirements of the DGIWG WMS application profile, DGIWG-112. A conforming implementation must also satisfy the constraints of the Queryable WMS conformance class as defined in the base WMS 1.3 standard.

You can use a Java IDE such as Eclipse, NetBeans, or IntelliJ to run the test suite. Clone the repository and build the project. The runtime configuration is summarized below.

Main class: de.latlon.ets.wms13.dgiwg.WmsDgiwgTestNGController

Arguments: The first argument must refer to an XML properties file containing the required test run argument (a reference to a WMS 1.3 capabilities document). If not specified, the default location of the file at ${user.home}/test-run-props.xml will be used.

You can modify the default settings in the sample test-run-props.xml file, which is shown below. The value of the wms argument must be an absolute URI that conforms to the 'http' or 'file' schemes. The tes argument specifies the location of a service that provides a RESTful API for running the base WMS 1.3 test suite; by default the OGC teamengine installation--the 'beta' facility--will be used, but an alternative installation may be used instead (for example: http://localhost:8080/teamengine).

Test run arguments

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties version="1.0">
  <comment>Test run arguments (ets-dgiwg-wms13)</comment>
  <entry key="wms"></entry>
  <entry key="vector">false</entry>
  <entry key="tes">http://cite.opengeospatial.org/te2/</entry>
</properties>

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

One of the build artifacts is an "all-in-one" JAR file that includes the test suite bundled together with all of its dependencies. This makes it very easy to execute the test suite in a command shell like so:

java -jar ets-dgiwg-wms-${version}-aio.jar [test-run-props.xml]

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

If you would like to get involved, you can:

• Report an issue such as a defect or an enhancement request
• Help to resolve an 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