W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2001

Test cases for SOAP 1.2 Part 2 Section 5

From: Volker Wiechers <volker.wiechers@sap.com>
Date: Mon, 17 Dec 2001 15:18:16 +0100
Message-ID: <3C1DFEA8.97877D2E@sap.com>
To: xml-dist-app@w3.org
At the F2F meeting in Boston, group 4 (N-Z) identified 4 testable
conditions
for section 5 of SOAP 1.2 part 2  (s.b).

Because of forthcomming major changes to the transport binding,
our group  decided to generate no testable condition for section 6
(old HPPT binding)

Regards,
    Volker



Testable conditions
----------------------

  Section 5: Using SOAP for RPC
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    5.1 (last paragraph):

       "Because a result indicates success and a fault indicates
        failure, it is an error for an RPC response to contain both a
        result and a fault".

      o Possible test: Send a non-idempotent header block and ensure
        that it won't get processed if there is a fault


    5.1 (bullet 6) (corresponds to Hugos Assertion A35) :

       "Each parameter accessor has a name corresponding to the name of
        the parameter and type corresponding to the type of the
parameter.
       The name of the return value accessor is 'result' and it is
       namespace-qualified with the namespace identifier
        'http://www.w3.org/2001/12/soap-rpc'. The return value accessor
       MUST be present if the return value of the procedure is non-void.

       The return value accessor MUST NOT be present if the return
        value of the procedure is void".

     o Two test cases (could be handled by Hugos echoOK function w/o
         return value)

       1) return value accessor must be present if return value <> void
           - (string) echoOK( void )
       2) return must not be present if return value  == void
           - (void) echoOK( out string )

    5.3 (3):
       "An rpc:ProcedureNotPresent fault MUST be generated when the
        server cannot find the procedure specified".

     o Call of an unknown function (echoOKunknown?)
        depending of the test suite this should generate an
        rpc:ProcedureNotPresent (for a generic SOAP RPC server) or
        "env:Client".

    5.3 (4):
       "An rpc:BadArguments fault MUST be generated when the server
        cannot parse the arguments or when there is a mismatch between
        what the server expects and what the client has sent".

     o Testability relies on test suite
     o Take echo service and add extra parameter
Received on Monday, 17 December 2001 08:16:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 22:28:13 UTC