-
Notifications
You must be signed in to change notification settings - Fork 3
Home
rjmartell edited this page Feb 19, 2016
·
22 revisions
The selection and execution of tests is rather tortuous. A test run starts off in WMTS_ETS.xml
and then executes the following steps:
- Fetch service metadata
- Note: XML Schema validation is disabled by default. Schematron is not used at all to perform rule-based validation (to check constraints that are beyond an XML Schema grammar).
- call-function "wmtsBootstrap:bootstrap.restful" (check advertised capabilities, e.g. for RESTful messaging)
- call-function "wmts:testMenus" (select tests)
- call-function "wmtsFunctions:invokeTestGroupsForBinding" (run test groups)
- call-function "wmtsFunctions:invokeSelectedTests" (in
wmtsFunctions.xml
) - call-test $testName
- call-function $functionName (in
wmtsFunctions.xml
; this file contains almost 30000 lines:exclamation:)
There is a draft ATS that offers some guidance regarding test coverage.
There are several test groups defined for each message encoding style described in the WMTS specification. Tests are associated with a test group in the bootstrap.xml
file (see table below).
Message encoding | Test groups |
---|---|
REST |
|
KVP |
|
SOAP |
|