|
version 1.16, 2005/12/08 16:31:48
|
version 1.17, 2006/05/31 21:59:06
|
|
|
|
| item 1: empty | item 1: empty |
| </test:send> | </test:send> |
| </programlisting></informalexample> | </programlisting></informalexample> |
| <para>SOAP requests are created in the same way as other XML requests, with a SOAP Envelope message body.</para> |
<para>SOAP requests are created in the same way as other XML requests, with a SOAP Envelope message body. they can be either literal or RPC, depending on the Envelope data.</para> |
| <informalexample><programlisting> | <informalexample><programlisting> |
| send a google SOAP request: | send a google SOAP request: |
| <test:send url="http://nowhere"> | <test:send url="http://nowhere"> |
|
|
|
| </test:attachment> | </test:attachment> |
| </test:send> | </test:send> |
| </programlisting></informalexample> | </programlisting></informalexample> |
| <para>XML responses can be verified in much the same way as HTML responses, to check content type, length etc. however, things like page title, forms and links obviously don't apply. the most powerful way to process an XML response is with the <command><test:verify test="xpath expression"/></command> construct, which gives you full access to the response content.</para> |
<para>binary attachments can be sent by referencing a file that contains the attachment.</para> |
| |
<informalexample><programlisting> |
| |
include a binary attachment: |
| |
<test:attachment location="img-1" href="images/funnybunny.jpg"/> |
| |
</programlisting></informalexample> |
| |
<para>XML responses can be verified in the same way as HTML responses, to check content type, length etc. however, things like page title, forms and links obviously don't apply. the most powerful way to process an XML response is with the <command><test:verify test="xpath expression"/></command> construct, which gives you full access to the response content.</para> |
| </section> | </section> |
| | |
| <section> | <section> |