%entities; ]>
&wsa-testsuite.title; &w3c-designation-wsa-testsuite; &document.status; &draft.day; &draft.month; &draft.year; &w3c-designation-wsa-testsuite; &altlocs; &prevloc; &wsa-testsuite.latest; Paul Downey BT

This document describes the Test Suite deliverable for the Web Services Addressing Working Group as defined by the Working Group's Charter.

&status; English

Last Modified: $Date: 2005/09/09 19:18:05 $
Introduction

One of the deliverables specified in the Charter of the Web Services Addressing Working Group is a test suite intended to promote implementation of the Candidate Recommendation, and to assess interoperability between these implementations.

The Working Group Charter also states that the Working Group is expected to demonstrate four interoperable implementations during the Call for Implementations step. It is anticipated that some, but not all of the test cases held within the test suite will be used to practically test implementations during an interoperability Workshop and thereby satisfy the entrance criteria for the Web Service Addressing specifications to enter the Proposed Recommendation stage.

The test suite will be maintained by the Working Group and remain available for regression testing beyond publication of the Web Addressing Recommendation, however it is not expected that the test suite will form a part of the Web Addressing Recommendation; the status of this document will remain as a Working Group note.

Conformance Claims

A Web Services Addressing implementation that passes all of the tests specified in this document may claim conformance to the Web Services Addressing Test Suite $Date: 2005/09/09 19:18:05 $.

Conformance to the Web services Addressing Test Suite does not by itself enable a party to claim conformance with the Web Services Addressing specification. Not passing an individual test may be used as an indication that an implementation is likely not to conform to the Web Services Addressing specification.

Notational Conventions

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [].

When describing abstract data models, this specification uses the notational convention used by the XML Infoset []. Specifically, abstract property names always appear in square brackets (e.g., [some property]).

When describing concrete XML schemas [, ], this specification uses the notational convention of WS-Security []. Specifically, each member of an element's [children] or [attributes] property is described using an XPath-like notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates the presence of an element wildcard (<xs:any/>). The use of @{any} indicates the presence of an attribute wildcard (<xs:anyAttribute/>).

 Test Cases

The Test Suite comprises of a collection of test cases. Each test case contains the following information:

An unambiguous xml:id value to enable the test case to be referenced within a specific version of the test suite.

A friendly name for the test case.

An indication that this test forms part of the Exit Criteria for the Candidate Recommendation phase for one or more Web Service Addressing specifications.

A list of assertions document the test case exhibits. The purpose of the assertions being to access the coverage of the Test Suite.

The concrete message exchange followed by a successful execution of the test case.

A list of the abstract scenarios exhibited by the test case, at most one from each of the categories: message passing, security, etc.

A description of the nature and characteristics of the test case to assist reviewers to understand the purpose of a test and provide those executing the test with any additional information that will be helpful should the test fail.

One or more example test documents, including WSDL 1.1 and WSDL 2.0 documents as well as SOAP 1.1 and SOAP 1.2 messages which may be used to build canned test interactions for some test cases.

 Contributing Test Materials

The Test Suite consists entirely of voluntary contributions of tests from interested parties. We encourage all members of the community to consider contributing any tests they may have developed to the Test Suite.

Tests may be submitted to the Suite in the form of an Email sent topublic-ws-addressing-tests@w3.org An archive is available athttp://lists.w3.org/Archives/Public/public-ws-addressing-tests Submited test cases should be released to the Test Suite by completing theTest Case Grant II Form.

When contributing materials to the Test Suite, it is helpful if each individual test case cites the metadata such as the existing Test Assertions, Scenarios and Message Exchanges exhibited. The submission may also include details of any new scenarios which the test case exhibits. Providing examples of the messages exchanged and metadata such as WSDL 1.1 and WSDL 2.0 in the form of complete XML documents will also be of value.

 References &wsa-core.title;, M. Gudgin, M. Hadley, Editors. &wsa-soap.title;, M. Gudgin, M. Hadley, Editors. &wsa-wsdl.title;, M. Gudgin, M. Hadley, Editors. Web Services Description Language 2.0, R. Chinnici, M. Gudgin, J. J. Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web Consortium, 3 August 2004. This version of the WSDL 2.0 specification is http://www.w3.org/TR/2004/WD-wsdl20-20040803. The latest version of WSDL 2.0 is available at http://www.w3.org/TR/wsdl20. Key words for use in RFCs to Indicate Requirement Levels, S. Bradner. Internet Engineering Task Force, June 1999. Available at http://www.ietf.org/rfc/rfc2119.txt. M. Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)", January 2005. Extensible Markup Language (XML) 1.0 (Third Edition), T. Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The latest version of XML 1.0 is available at http://www.w3.org/TR/REC-xml. Namespaces in XML, T. Bray, D. Hollander, and A. Layman, Editors. World Wide Web Consortium, 14 January 1999. This version of the XML Information Set Recommendation is http://www.w3.org/TR/1999/REC-xml-names-19990114. The latest version of Namespaces in XML is available at http://www.w3.org/TR/REC-xml-names. XML Information Set, J. Cowan and R. Tobin, Editors. World Wide Web Consortium, 24 October 2001. This version of the XML Information Set Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The latest version of XML Information Set is available at http://www.w3.org/TR/xml-infoset. XML Schema Part 1: Structures Second Edition, H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 28 October 2004. This version of the XML Schema Part 1 Recommendation is http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The latest version of XML Schema Part 1 is available at http://www.w3.org/TR/xmlschema-1. XML Schema Part 2: Datatypes Second Edition, P. Byron and A. Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This version of the XML Schema Part 2 Recommendation is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The latest version of XML Schema Part 2 is available at http://www.w3.org/TR/xmlschema-2. SOAP Version 1.2 Part 1: Messaging Framework, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web Consortium, 24 June 2003. This version of the "SOAP Version 1.2 Part 1: Messaging Framework" Recommendation is http://www.w3.org/TR/2003/REC-soap12-part1-20030624/. The latest version of "SOAP Version 1.2 Part 1: Messaging Framework" is available at http://www.w3.org/TR/soap12-part1/. OASIS, Web Services Security: SOAP Message Security, March 2004. &acknowledgements; Change Log