https://github.com/opengeospatial/ets-wms13-dgiwg
https://github.com/opengeospatial/ets-wms13-dgiwg
Last synced: 6 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/opengeospatial/ets-wms13-dgiwg
- Owner: opengeospatial
- Created: 2016-11-30T15:46:11.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2025-06-17T17:41:54.000Z (about 1 year ago)
- Last Synced: 2025-06-17T18:41:59.238Z (about 1 year ago)
- Language: Java
- Size: 894 KB
- Stars: 0
- Watchers: 8
- Forks: 2
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Test Suite for the DGIWG WMS Profile
This test suite verifies that a Web Map Service (WMS) component meets the requirements of the
DGIWG WMS application profile, [DGIWG-112](https://portal.dgiwg.org/files/?artifact_id=11514]).
A conforming implementation must also satisfy the constraints of the **Queryable WMS** conformance
class as defined in the base [WMS 1.3 standard](http://www.opengeospatial.org/standards/wms).
## How to run the tests
### Integrated development environment (IDE)
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](src/main/config/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**
|Argument |Description |Default value |
|:---------|:------------|:---------------|
|wms |Location of WMS capabilities document |
|vector |Are any layers derived from vector data? |false
|tes |Endpoint for test execution service |http://cite.opengeospatial.org/te2/
```xml
Test run arguments (ets-dgiwg-wms13)
false
http://cite.opengeospatial.org/te2/
```
The TestNG results file (testng-results.xml) will be written to a subdirectory
in ${user.home}/testng/ having a UUID value as its name.
### Command shell (terminal)
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]`
### OGC test harness
Use [TEAM Engine](https://github.com/opengeospatial/teamengine), the official
OGC test harness. The latest test suite release should be available at the
[beta testing facility](http://cite.opengeospatial.org/te2/). You can also
[build and deploy](https://github.com/opengeospatial/teamengine) the test
harness yourself and use a local installation.
## How to contribute
If you would like to get involved, you can:
* [Report an issue](https://github.com/opengeospatial/ets-dgiwg-wms13/issues) such as a defect or an
enhancement request
* Help to resolve an [open issue](https://github.com/opengeospatial/ets-dgiwg-wms13/issues?q=is%3Aopen)
* 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