Forum Discussion
maxfactor
13 years agoOccasional Contributor
I had a very very similar problem and this posted solution fixed it.
I had just one simple mock response with no query match at all. I started the Mock response engine and then generated the request and received "Failed to find MockResponse" error from SoapUI. So I looked in my project file and I found:
<con:defaultResponse>Response 1</con:defaultResponse><con:response name="MockResponse 2"
MY Mock response is really named "MockResponse 2" and I have no idea where the default name "Response 1" came from but I changed the default to also be "MockResponse 2", re-ran the test and then the Mock response was generated.
Thanks Bhlem!
I am using SoapUI 2.5.2 Pro on a Windows 7 machine.
This seems like a bug that has been around since the original post in 2011.
I had just one simple mock response with no query match at all. I started the Mock response engine and then generated the request and received "Failed to find MockResponse" error from SoapUI. So I looked in my project file and I found:
<con:defaultResponse>Response 1</con:defaultResponse><con:response name="MockResponse 2"
MY Mock response is really named "MockResponse 2" and I have no idea where the default name "Response 1" came from but I changed the default to also be "MockResponse 2", re-ran the test and then the Mock response was generated.
Thanks Bhlem!
I am using SoapUI 2.5.2 Pro on a Windows 7 machine.
This seems like a bug that has been around since the original post in 2011.