W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > September 2010

WWW/2002/ws/ra/edcopies wsmex-test.html,NONE,1.1 wsmex-test.xml,NONE,1.1

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 21 Sep 2010 15:37:21 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Oy4uH-0002m5-Tg@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv10556

Added Files:
	wsmex-test.html wsmex-test.xml 
Log Message:
Some initial tests


--- NEW FILE: wsmex-test.html ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title>WS-MetadataExchange Test Document </title><link href="spec-tests.css" type="text/css" rel="stylesheet"></link></head><body><p>
      This is the test doc for 
      <a href=" http://www.w3.org/2002/ws/ra/edcopies/wsmex.html ">WS-MetadataExchange</a>. Boilerplate
      header information will go here...
     </p><hr></hr><h1>Table of Contents</h1><ol><li><a href="#sec-F1">
         Feature F1:
          Metadata Collecton </a></li><li><a href="#sec-F2">
         Feature F2:
          GetWSDL </a></li><li><a href="#sec-F3">
         Feature F3:
          GetMetadata </a></li><li><a href="#sec-F4">
         Feature F4:
          feature 2 </a></li></ol><hr></hr><p> 
  This test suite will exercise the features defined by WS-MetadataExchange.
 </p><hr><a name="sec-F1"></a><div><h1> 
     Feature:  Metadata Collecton <span class="note">(F1)</span></h1><div class="featureBox"><p><description>
   The MEX specification defines a new type of metadata called a
   Metadata collection. It provides a way to bundle multiple pieces
   of metadata into one XML document. 
  </description></p><div class="testBox"><h2>Test: Retrieving a Metadata Collection<span class="note">
        (T1.1)
      </span></h2><p><description>
    This test will verify the basic structure of a the Metadata collection
    type. Since support for this data type and the GetMetadata operation
    are optional, this test is optional.
   </description><br><br><b>Success Criteria:</b><br><success>
    A client sends a GetMetadata request and the service responds with
    a GetMetadataResponse in the Body. The contents of the metadata
    embedded within the Metadata collection is not important for this test.
   </success></p></div><p class="ieSpacer"><br></p><div class="testBox"><h2>Test: Empty Metadata Collection<span class="note">
        (T1.2)
      </span></h2><p><description>
    This test will verify the basic structure of an empty Metadata collection
    type. Since support for this data type and the GetMetadata operation
    are optional, this test is optional.
   </description><br><br><b>Success Criteria:</b><br><success>
    A client sends a GetMetadata request that asks for a metdata type
    that is unknown to the service, and the service responds with
    an empty GetMetadataResponse in the Body.
    <br>
    For the purpose of this test, a Dialect QName of:
      <xmp> {http://example.com/:bogusDialect} </xmp>
    will be used for the unknown metadata type.
   </success></p></div><p class="ieSpacer"><br></p><div class="testBox"><h2>Test: Metadata Collection Identifiers<span class="note">
        (T1.3)
      </span></h2><p><description>
    This test will verify that when the Dialect QName of a MetadataSection
    matches one of the predefined QNames specified in the MEX specification,
    then the <code>@Identifier</code> value is set correctly.
   </description><br><br><b>Success Criteria:</b><br><success>
    A client sends a GetMetadata request that asks for 3 different types
    of Metadata (Schema, WSDL and Policy). If the service returns any
    of those types then the MetadataSections for each must have a 
    <code>@Identifier</code>
    attribute that matches the table in the MEX specification. 
    Specifically:
     <table border="1"><tr><td><b>Metadata Type</b></td><td><b>@Identifier</b></td></tr><tr><td>Schema</td><td>xs:schema/@targetNamespace</td></tr><tr><td>WSDL</td><td>wsdl:definitions/@targetNamespace</td></tr><tr><td>Policy</td><td>wsp:Policy/@Name</td></tr></table></success></p></div><p class="ieSpacer"><br></p></div></div><hr><a name="sec-F2"></a><div><h1> 
     Feature:  GetWSDL <span class="note">(F2)</span></h1><div class="featureBox"><p><description> 
   The GetWSDL operation is used to retrieve the WSDL from a service.
   It is the SOAP equivalent of the ?wsdl feature that many implementations
   support today.
  </description></p><div class="testBox"><h2>Test: GetWSDL<b> (required)</b><span class="note">
        (T2.1)
      </span></h2><p><description> 
    Tests that an endpoint supports returning its WSDL in response
    to a GetWSDL request. A compliant serice is required to support this.
   </description><br><br><b>Success Criteria:</b><br><success> 
     A client sends a GetWSDL request and the service responds with
     a GetWSDLResponse in the Body. Note, the GetWSDLResponse can be
     empty (meaning there is no WSDL), can have the service's WSDL as
     its child element, or the GetWSDLResponse may contain a reference
     (mex:Location, mex:Reference) to a metadata resource representing
     the WSDL.
   </success></p></div><p class="ieSpacer"><br></p></div></div><hr><a name="sec-F3"></a><div><h1> 
     Feature:  GetMetadata <span class="note">(F3)</span></h1><div class="featureBox"><p><description>
   The GetMetadata operaton is used to retrieve metadata from an 
   endpoint. It allows client to ask for all metadata or specific
   types. It also allows clients to specify the form in which the metadata
   is returned - inlined or a reference.
  </description></p><div class="testBox"><h2>Test: GetMetadata success<span class="note">
        (T3.1)
      </span></h2><p><description> 
    Tests than an endpoint supports returning
   </description><br><br><b>Success Criteria:</b><br><success> success criteria .
     The xml should look like this:
     <xmp><foo>hello</foo></xmp></success></p></div><p class="ieSpacer"><br></p></div></div><hr><a name="sec-F4"></a><div><h1> 
     Feature:  feature 2 <span class="note">(F4)</span></h1><div class="featureBox"><p><description> blah blah blah </description></p><div class="testBox"><h2>Test: t2<b> (required)</b><span class="note">
        (T4.1)
      </span></h2><p><description> test1 test1 test2 </description><br><br><b>Success Criteria:</b><br><success> success criteria .
     The xml should look like this:
     <xmp><foo>hello</foo></xmp></success></p></div><p class="ieSpacer"><br></p></div></div></body></html>
--- NEW FILE: wsmex-test.xml ---
<?xml-stylesheet type='text/xsl' href='spec-tests.xsl'?>
<spec name="WS-MetadataExchange" xmlns="http://w3.org/test">
 <url> http://www.w3.org/2002/ws/ra/edcopies/wsmex.html </url>

 <description> 
  This test suite will exercise the features defined by WS-MetadataExchange.
 </description>

 <feature>
  <name> Metadata Collecton </name>
  <description>
   The MEX specification defines a new type of metadata called a
   Metadata collection. It provides a way to bundle multiple pieces
   of metadata into one XML document. 
  </description>

  <test name="Retrieving a Metadata Collection" optional="true">
   <description>
    This test will verify the basic structure of a the Metadata collection
    type. Since support for this data type and the GetMetadata operation
    are optional, this test is optional.
   </description>
   <success>
    A client sends a GetMetadata request and the service responds with
    a GetMetadataResponse in the Body. The contents of the metadata
    embedded within the Metadata collection is not important for this test.
   </success>
  </test>

  <test name="Empty Metadata Collection" optional="true">
   <description>
    This test will verify the basic structure of an empty Metadata collection
    type. Since support for this data type and the GetMetadata operation
    are optional, this test is optional.
   </description>
   <success>
    A client sends a GetMetadata request that asks for a metdata type
    that is unknown to the service, and the service responds with
    an empty GetMetadataResponse in the Body.
    <br/>
    For the purpose of this test, a Dialect QName of:
      <xmp> {http://example.com/:bogusDialect} </xmp>
    will be used for the unknown metadata type.
   </success>
  </test>

  <test name="Metadata Collection Identifiers" optional="true">
   <description>
    This test will verify that when the Dialect QName of a MetadataSection
    matches one of the predefined QNames specified in the MEX specification,
    then the <code>@Identifier</code> value is set correctly.
   </description>
   <success>
    A client sends a GetMetadata request that asks for 3 different types
    of Metadata (Schema, WSDL and Policy). If the service returns any
    of those types then the MetadataSections for each must have a 
    <code>@Identifier</code>
    attribute that matches the table in the MEX specification. 
    Specifically:
     <table border="1">
      <tr> <td><b>Metadata Type</b></td> <td><b>@Identifier</b></td> </tr>
      <tr> <td>Schema</td> <td>xs:schema/@targetNamespace</td> </tr>
      <tr> <td>WSDL</td> <td>wsdl:definitions/@targetNamespace</td> </tr>
      <tr> <td>Policy</td> <td>wsp:Policy/@Name</td> </tr>
     </table>
   </success>
  </test>

 </feature>

 <feature>
  <name> GetWSDL </name>
  <description> 
   The GetWSDL operation is used to retrieve the WSDL from a service.
   It is the SOAP equivalent of the ?wsdl feature that many implementations
   support today.
  </description>

  <test name="GetWSDL" optional="false">
   <description> 
    Tests that an endpoint supports returning its WSDL in response
    to a GetWSDL request. A compliant serice is required to support this.
   </description>
   <success> 
     A client sends a GetWSDL request and the service responds with
     a GetWSDLResponse in the Body. Note, the GetWSDLResponse can be
     empty (meaning there is no WSDL), can have the service's WSDL as
     its child element, or the GetWSDLResponse may contain a reference
     (mex:Location, mex:Reference) to a metadata resource representing
     the WSDL.
   </success>
  </test>
 </feature>

 <feature>
  <name> GetMetadata </name>

  <description>
   The GetMetadata operaton is used to retrieve metadata from an 
   endpoint. It allows client to ask for all metadata or specific
   types. It also allows clients to specify the form in which the metadata
   is returned - inlined or a reference.
  </description>

  <test name="GetMetadata success" optional="true">
   <description> 
    Tests than an endpoint supports returning
   </description>
   <success> success criteria .
     The xml should look like this:
     <xmp>
      <foo>hello</foo>
     </xmp>
   </success>
  </test>
 </feature>

 <feature>
  <name> feature 2 </name>
  <description> blah blah blah </description>

  <test name="t2">
   <description> test1 test1 test2 </description>
   <success> success criteria .
     The xml should look like this:
     <xmp>
      <foo>hello</foo>
     </xmp>
   </success>
  </test>
 </feature>

</spec>
Received on Tuesday, 21 September 2010 15:37:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 21 September 2010 15:37:24 GMT