Features:
UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to true. The presence of WS-A headers is tested in request and response message.
Port: wsaTestPortTypePortAddressingRequired
Features:
UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to true. The WS-A headers are absent on the request message and a fault message is returned on the HTTP response.
Port: wsaTestPortTypePortAddressingRequired
Features:
UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to true. The presence of WS-A headers is tested in request and response message.
Port: wsaTestPortTypePortAddressingRequiredOnPort
Features:
UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to true. The WS-A headers are absent on the request message and a fault is returned on the HTTP response.
Port: wsaTestPortTypePortAddressingRequiredOnPort
Features:
UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to false. The presence of WS-A headers is tested in request and response message.
Port: wsaTestPortTypePortAddressingNotRequired
Features:
UsingAddressing appear as child of wsdl:binding and wsdl:required attribute is set to false. The WS-A headers are absent on the request message. A response message is returned on the HTTP response. If WS-A headers are present in response then they must not be marked mustUnderstand=true.
Port: wsaTestPortTypePortAddressingNotRequired
Features:
UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to false. The presence of WS-A headers is tested in request and response message.
Port: wsaTestPortTypePortAddressingNotRequiredOnPort
Features:
UsingAddressing appear as child of wsdl:port and wsdl:required attribute is set to false. The WS-A headers are absent on the request message. A response message is returned on the HTTP response. If WS-A headers are present in response then they must not be marked mustUnderstand=true.
Port: wsaTestPortTypePortAddressingNotRequiredOnPort
Features:
An explicit wsaw:Action is specified on the input and output message. The presence of correct Action header is checked on the request and response message.
Port: wsaTestPortTypePortExplicitAction
Features:
An explicit wsaw:Action is specified on the input and output message. The request message contains an incorrect Action header. A fault message is returned on the HTTP response indicating the nature of fault.
Port: wsaTestPortTypePortExplicitAction
Features:
An explicit wsaw:Action is specified on the input and fault message. Application fault message is returned on the HTTP response. The presence of correct Action header is checked on the request and fault message.
Port: wsaTestPortTypePortExplicitAction
Features:
The wsdl:portType contain two request-response operations with same message body for the request message, different wsaw:Action values and different message bodies for the response message. assertion: confirm that the correct response body is returned based on the specified action value
Port:
Features:
wsdl port type containing two req/resp operations the message body for the request is the same with default action and different response message bodies. assertion: confirm that the correct response body is returned based on the specified action value
Port: wsaTestPortTypePortAddressingRequired
Features:
No wsaw:Action on the input and output message of the operation. The presence of implicit Action is checked on the request and response message.
Port: wsaTestPortTypePortAddressingRequired
Features:
No wsaw:Action on the input and output message of the operation. The request message contains an incorrect Action header. A fault message is returned on the HTTP response indicating the nature of fault.
Port: wsaTestPortTypePortAddressingRequired
Features:
No wsaw:Action on the input and fault message of the operation. Application fault message is returned on the HTTP response. The presence of correct Action header is checked on the request and fault message.
Port: wsaTestPortTypePortAddressingRequired
Features:
Normal WSDL (same as we have been using) with no action value specified and SOAPAction specified in binding. assertion: client sends action value the same as SOAPAction and server responds with correct response
Port: wsaTestPortTypePortSoapAction
Features:
Normal WSDL (same as we have been using) with no action value specified and SOAPAction specified in binding. assertion: client sends action incorrect action and server returns appropriate fault
Port: wsaTestPortTypePortSoapAction
Features:
The WSDL has a target namespace using urn scheme. The presence of correction Action header is checked on the request and response message.
Port:
Features:
The WSDL has a target namespace using urn scheme. No wsaw:action is specified on the input and output message. The request message contains an incorrect Action header. A fault message is received on the HTTP response with approrpiate fault code/subcode.
Port: wsaTestPortTypePortAddressingRequired
Features:
The WSDL has a target namespace using urn scheme. No wsaw:Action on the input and fault message of the operation. Application fault message is returned on the HTTP response. The presence of correct Action header is checked on the response message.
Port: wsaTestPortTypePortAddressingRequired
Features:
The binding of a request-response operation specify wsaw:Anonymous=required. The request message contains anonymous ReplyTo. A response message is returned on the HTTP response.
Port: wsaTestPortTypePortAnonymousRequired
Features:
The binding of a request-response operation specify wsaw:Anonymous=required. The request message contains non-anonymous ReplyTo. A fault message is returned on the HTTP response with approrpiate fault code/subcode.
Port: wsaTestPortTypePortAnonymousRequired
Features:
The binding of a request-response operation specify wsaw:Anonymous=required. The request message contains non-anonymous FaultTo. A fault message is returned on the HTTP response with approrpiate fault code/subcode.
Port: wsaTestPortTypePortAnonymousRequired
Features:
The binding of a request-response operation specify wsaw:Anonymous=prohibited. The request message contains non-anonymous ReplyTo. A response message is returned on the ReplyTo address.
Port: wsaTestPortTypePortAnonymousProhibited
Features:
The binding of a request-response operation specify wsaw:Anonymous=prohibited. The request message contains an anonymous ReplyTo and non-anonymous FaultTo. A fault message is returned on the FaultTo address.
Port: wsaTestPortTypePortAnonymousProhibited
Features:
The binding of a request-response operation specify wsaw:Anonymous=prohibited. The request message contains anonymous ReplyTo and FaultTo. A fault message is returned on the TBD.
Port: wsaTestPortTypePortAnonymousProhibited
Features:
The binding of a request-response operation specify wsaw:Anonymous=prohibited. The request message contains anonymous ReplyTo.
Port: wsaTestPortTypePortAnonymousProhibited
Features:
The binding of a request-response operation specify wsaw:Anonymous=optional. The request message contains non-anonymous ReplyTo. A response message is returned on the ReplyTo address.
Port: wsaTestPortTypePortAnonymousOptional
Features:
The binding of a request-response operation specify wsaw:Anonymous=optional. The request message contains non-anonymous FaultTo. Application fault message is returned on the FaultTo address.
Port: wsaTestPortTypePortAnonymousOptional
Features:
The binding of a request-response operation specify wsaw:Anonymous=optional. The request message contains anonymous ReplyTo. A response message is returned on the HTTP response.
Port: wsaTestPortTypePortAnonymousOptional
Features:
The binding of a request-response operation specify wsaw:Anonymous=optional. The request message contains anonymous FaultTo. Application fault message is returned on the HTTP response.
Port: wsaTestPortTypePortAnonymousOptional
Generated from testcases.xml using
testcases.xsl.
$Date: 2006/07/28 16:55:55 $
Copyright © 2006 W3C ® ( MIT , ERCIM ,Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public andMember privacy statements.