Hi Rupert,
Thanks again for the response.
Another question:
The XML response that got generated automatically. Where does it come from? And how does SOAP UI know what tags is needed for the response?
Same goes for the request (step 4.4). And when it says it changes the endpoint automatically. That means, internally, the request is been pointed to the endpoint of the mock service - to invoke the response.
Overall, my aim is to develop a mock service that behaves like an actual services that exists. This service has a number of methods it understands. I need to simulate all these methods, with thier corresponding outputs.
Now, I have a service in Visual Studio that will query this mock service. Since I'm expecting a number of different responses, I now know it means I will have multiple responses.
Question is, how do I tell SOAP UI to look out for certain requests and give the corresponding responses?
In addition to the questions above, I was able to find a SOAP UI project a colleague worked on (who I have no contact with anymore). In his mockservice, there is no operation (and no response), but he made use of the 'OnRequest Script' - which is described as "a groovy script to run when receiving a request before it is dispatched".
This contradicts the tutorial. How does it fit in? Can one really make use of the OnRequest script to generate the required XML response?
If there is any additional reading material you feel I should read, please feel free to advise. Asides from your book ofcourse.
Your response, as always, is appreciated.
Kind regards,
Michael