- act like a normal web services client and perform asserts on the returned result
- use WebTest (with either the XML or Groovy syntax)
- use SoapUI (for functional and load testing)
We are going to use the Web Service example at:
The first approach (traditional webtest) produces more information in the test summary reporting but requires you to do more work (i.e. keep the requests around as XML). It depends if you already have those XML files around for other purposes, e.g. manual testing.
//soapui.org/ is a SOAP functional and load testing tool. It can use Groovy steps within its testcases. For further details, see the soapui documentation for the Groovy Step. This step supports data-driven tests, allows control of test execution and allows customised reporting.