XML Encoding Validity XML Validation Exception Reporting

222 Copyright © 2011 Open Geospatial Consortium b Test Method: For all SPS operations supported by the service, create an XML request instance that is invalid according to its schema definition outlined in Table 82 and send it to the service. Verify that the service returns an exception with code InvalidRequest. c Reference: 7.2, 12 d Test Type: Basic

11.10 Conformance Class – SOAP

http:www.opengis.netspecSPS2.0confSOAP

11.10.1 Capability Test

http:www.opengis.netspecSPS2.0confSOAPCapability a Test Purpose: Verify that the server implements the SOAP conformance class. b Test Method: Verify that the server implements the XML Encoding conformance class. Do so by checking that the Body element in SOAP messages sent to the service for invoking an SPS operation contains a valid XML representation of the according operation request. Verify that the server implements the http:www.opengis.netspecSWES2.0confSOAPBinding conformance classes. Verify the conformance tests listed in section 11.10.2. c Reference: see references in conformance tests d Test Type: Capability

11.10.2 Modules with Basic Tests

11.10.2.1 Action URIs

11.10.2.1.1Asynchronous request response http:www.opengis.netspecSPS2.0confSOAPActionURIsAsyncRequestResponse a Test Purpose: To verify that WS-Addressing is used to enable asynchronous request response. b Test Method: Get the service metadata WSDL and or Capabilities document. Ensure that the service metadata does not indicate support for any asynchronous request response realization technique that could be used by clients other than WS-Addressing. c Reference: 9.5 d Test Type: Basic Copyright © 2011 Open Geospatial Consortium 223 11.10.2.1.2Operation Actions http:www.opengis.netspecSPS2.0confSOAPActionURIsOperationActions a Test Purpose: To verify that the service recognizes and uses correct action URIs for operation requests and responses as well as notifications as defined in this standard. b Test Method: Depending upon the SOAP binding available at the service, execute a request for each SPS operation supported by the service. Verify that the service uses the correct SOAP action as defined in Table 68 or uses an empty action in its response. If WS-Addressing is used, verify that the service uses the correct WS- Addressing action URIs as defined in Table 68. c Reference: 9.3 d Test Type: Basic

11.10.2.2 Exception Handling

11.10.2.2.1Usage of SOAP faults http:www.opengis.netspecSPS2.0confSOAPExceptionHandlingSOAPFaultUsage a Test Purpose: Verify that SOAP faults for the SPS operations are encoded correctly. Test Method: For each SPS operation supported by the service, create one SOAP encoded request that causes an exception with certain code. For each operation, repeat this so that one test request for all applicable exception codes as listed in b Figure 12 is available. Send the requests to the service. Verify that the service returns a SOAP fault as defined in OGC 09-001 clause 19.2 and clause 9.2 in this standard. c Reference: 9.2, OGC 09-001 clause 19.2 d Test Type: Basic

11.10.2.3 Service Metadata

11.10.2.3.1SOAP operation encoding advertised http:www.opengis.netspecSPS2.0confSOAPServiceMetadataOperationEncodingAdvertisement a Test Purpose: Verify that the service indicates that it supports the SOAP binding. b Test Method: Devise a GetCapabilities request and send it to the service to retrieve the operationsMetadata section of the capabilities document. Verify that a PostEncoding constraint for the HTTP POST transfer of all operations exists that has the value SOAP.