catch timeout of Mock Response TestStep
Dear SoapUI community, I would like to test an async callback is NOT triggered within the timeout that was specified in the Mock Response TestStep. The testcase contains 2 TestSteps: 1 - Test Req...
Forum Discussion
Hi Rao,
Thank you for the link. I am totally aware of the functionality of the Mock TestStep. The problem is that SoapUI does not support this kind of negative test scenario out of the box.
From the description it's clear that the timeout is stopping the execution of the TestSteps:
I also have no chance to handle it in a script of the MockResponse - as this is only triggered once there is a request.
What I want to achieve is to wait for ~1000ms (timeout) and if nothing was received during that time - the TestStep shall be threated as successfull.
Maybe I have to set the timeout to 0 (while setting the StartStep to the TestStep that could trigger the unwanted request) and stop the MockResponse TestStep in another groovy TestStep after a short sleep (timeout). I'll give it a try and report back my findings.
Thank you for the link. I am totally aware of the functionality of the Mock TestStep. The problem is that SoapUI does not support this kind of negative test scenario out of the box.
From the description it's clear that the timeout is stopping the execution of the TestSteps:
Timeout - Fails the MockResponse Step if no request has been received within the specified number of milliseconds. Specifying 0 will wait indefinitely.
I also have no chance to handle it in a script of the MockResponse - as this is only triggered once there is a request.
What I want to achieve is to wait for ~1000ms (timeout) and if nothing was received during that time - the TestStep shall be threated as successfull.
Maybe I have to set the timeout to 0 (while setting the StartStep to the TestStep that could trigger the unwanted request) and stop the MockResponse TestStep in another groovy TestStep after a short sleep (timeout). I'll give it a try and report back my findings.