Expecting no request in MockResponse step
I was wondering if anyone has any strategies for verifying the situation where you are expecting your MockResponse step to never receive a request. Our web service sends out data alerts as requests...
Forum Discussion
I have a similar need to assert that my system does not send a message.
I like the approach that Ole gives, but the issue that I am running into is that the mock service is not started fast enough.
I started by trying to create a failing test (where my system "incorrectly" sends a message to the mock service). I did this by:
- soapui sends message to my system. (Receiving this message triggers my system to send out a message to the mock service)
- soapui groovy script launches mock service step, asserting that a timeout occurs
It looks like my service attempts to send message to the mock service prior to the mock service actually starting.
Feature request: option in the mock service to assert that no message was received.
I like the approach that Ole gives, but the issue that I am running into is that the mock service is not started fast enough.
I started by trying to create a failing test (where my system "incorrectly" sends a message to the mock service). I did this by:
- soapui sends message to my system. (Receiving this message triggers my system to send out a message to the mock service)
- soapui groovy script launches mock service step, asserting that a timeout occurs
It looks like my service attempts to send message to the mock service prior to the mock service actually starting.
Feature request: option in the mock service to assert that no message was received.