In order to get started with service testing, you should first understand four key terms. The test engine is a software product that can run scripts. A test script is an XML file that describes a request to send to a server, and an expected response from the server. Test scripts are often referred to as simply tests. We currently have a set of test scripts for the following services (versions in parentheses):

• Catalog Service-Web (CSW 2.0.2)
• Sensor Observation Service (SOS 1.0.0)
• Sensor Planning Service (SPS 1.0)
• Web Coverage Service (WCS 1.0.0)
• Web Feature Service (WFS 1.1 & WFS 1.0.0)
• Web Map Context (WMS 1.1.0)
• Web Map Service (WMS 1.3 & WMS 1.1.1)
• Web Registry Service (WRS 1.0)
• GeoRSS validation
• GML Validation

Our set of tests are the official ones, and the ones required for compliance certification. When you want to run a set of tests against a specific server, we call that a test session. A test session saves the server and test information along with a record of which tests have passed or failed. This allows you to come back another day and pick up where you left off.

The final term to know is test data. Compliance tests are much more predictable (and shorter!) when everyone tests with the same data. To pass all of the official WCS, WFS and WMS tests, you will need to install the appropriate test data on your server. The engine may be able to run some of the tests even if you skip this step, but most of the tests depend on the dataset, so a much larger set of tests will be executed when the dataset is properly implemented. The service will not pass certification testing if you skip this step.

With this terminology in mind, you should have little trouble following the more thorough instructions below that guide you through the steps of:

1. Creating an account
2. Creating a test session
3. Executing tests
4. Examining test results

The compliance process ends with certification. This is an off-line procedure which can be initiated by contacting OGC at compliance@opengeospatial.org.

Beta Tests
Test implementations of unofficial test suites not yet available for certification.

Catalogue Services/Web 2.0.1
Test implementations of Catalogue Services/Web 2.0.1.

Web Coverage Service 1.0.0
Test implementations of Web Coverage Service 1.0.0.

Web Feature Service 1.0.0
This test engine is designed to test implementations of the Web Feature Service 1.0.0 with filters defined using OGC Filter Encoding 1.0.0 specification and features defined using Geography Markup Language 2.1.2 specification.

Web Feature Service 1.1
This test suite is designed to test implementations of the Web Feature Service 1.1.0 with filters defined using OGC Filter Encoding 1.0.0 specification and features defined using the Geography Markup Language 3.1.1 simple Features Profile 1.0 specification.

Web Map Service 1.1.1
Test implementations of Web Map Service 1.1.1 servers. Certification does require the loading of specific data sets available in GML, MapInfo, and Shapefile formats.

Web Map Service 1.3
Test implementations of Web Map Service 1.3 servers. Certification does require the loading of specific data sets available in GML, MapInfo, and Shapefile formats.

Geography Markup Language 2.1.2
The GML 2.1.2 test engine supports the validation of GML 2.1.2 schemas and instance documents.

GeoRSS
Validates GeoRSS encoded RSS feeds (GeoRSS is designed for use with Atom 1.0, RSS 2.0, and RSS 1.0. More info on GeoRSS.

Web Map Context 1.1.0
Validate WMC 1.1.1 instance documents.