Forum Discussion
4 Replies
- omatzuraSuper ContributorHi!
well.. if the web-service returns no response at all and there is no other way of checking its state then you would either have to extend the webservice so it somehow makes its state available for testing or inspect the webservices container (if possible) to see that the webservice is "working ok"..
hmm.. any other ideas someone?
regards!
/Ole
eviware.com - richard_mccarthContributorHi Ole,
Would it be possible to add a new feature to SOAP UI to extend the mocking so that an async one-way web service could be mocked, have a script process the request and select the request to send back as a client to another async web service, rather than a response sent back from a mock service in the current mocking implementation.
This would allow round-trip mocking of async web services where replies get sent later. This would not need to much code as the scripting part already exists and it would be very very useful
What do you think, I hope I have'nt just overlooked it in the documentation,
Richard - omatzuraSuper ContributorHi Richard,
thanks for your ideas! You could achieve this by preparing a testcase containing the request(s) you want to send "back" and then running that testcase via groovy from the dispatch script of your mockoperation. Does that sound feasible?
regards!
/Ole
eviware.com - Hi All,
I need to do a load test for an asynchronous web service call.
Can this be done. Please let me know
1. create a test case and send a request
2. get the response (Acknowlegdement as soon as we submit the request)
3. Wait for the actual response using a mock service ?
This mock service should pick up the second response from the server
Any help is highly appreciated.