Royd wrote:How do you recommend using eValid to test a web service?
The key thing to remember is that eValid is a browser with test functionality built inside.
A typical web service has [somewhere] a description that shows how you can access the data from each object that is supported by a web service into a web page. That is, into HTML.
We'll kook this up and post about it later on, but there are some available systems that automatically generate an HTML web page from the WSDL's for the web service.
Where eValid comes in is this: With such a web page available to you, it is almost trivial to test the web service by feeding in data and retrieving response data...all from an HTML page.
This is a case of the time-honored technique of "reducing the problem [of testing a web service] to a previously solved problem [testing an HTML page]."
eValid Support