Our soapUI does seem to ignore the 'Start Step' property of mockresponse steps.
How to reproduce: take a soapUIPro 4.0.0 or 4.0.1
make a testcase, add (e.g.) a request
after the request add a delay (say 3sec)
after the request add a mockresponse and set its start step property to the request step.
in the soapUI log you will see that the mockservice for the mockresponse gets started after the delay, not before.
in 4.0.0 this usually broke our tests of asynchronous services, as the response was already gone when the mockResponse started triggering
(we had to add a delay on the asynchronous service as workaround). In 4.0.1 it seems to work, but i'm not sure if soapUI queues the requests or we are just lucky.
Best regards,
Pat
