This executable test suite is based on the following documents:
The only difference in testing an implementation of the original WCS 1.0.0 spec (03-065r6) or the corrigendum (05-076) is the schemas used for validation. Both are tested using test module wcs1-0-0:main in the abstract test suite. When the test suite is started, the user can select which version of the schemas is implemented.
The tests performed against an implementation are selected based on the capabilities document for the WCS implementation. By omitting a request, operation or capability from the capabilities document the tests for that functionality will not be executed against the implementation. The test suite makes a few basic assumptions about the WCS:
There is no standard MIME header definitions for the 5 required formats. Thus the actual MIME header depends on the server. The assertion test will check the results based on the first available format for the first coverage. A MIME header value should be entered during session configuration.
The WCS spec allows servers to use an UpdateSequence value for maintaining cache consistency. If the server advertises an UpdateSequence value then values that are lexically higher and lower than the current updateSequence value should be entered during session configuration.
Those values are required to test GetCoverage with parameter RESX and RESY. The values depends on the crs provided by the first offering. Values for RESX and RESY should be entered during session configuration.
The following test scopes will be tested automatically:
Only the protocol is tested.
Each encoding is optional except for the GetCapabilities GET KVP encoding. The optional encodings are only tested when the GetCapabilities response indicates that the encoding is supported.
The user is prompted for the end point URL of the server. If there is no server at that location, the testing stops.
The schemas for the corrigendum are currently available online at http://schemas.opengis.net/wcs/1.0.0.
Details on the tests performed are available in the abstract test suite.
Release notes are available from the relnotes.html.