Mock Service responds but the test case does not progress
Hi,
I am using SOAP UI 4.0.0 for testing an integration project with several several Web Services. I am facing a strange behavior which happens randomly in one of our test cases. The test case (attached) has several steps including few SOAP requests and Mock services.
When I execute it, sometimes test case get stuck in some Mock Services as if the Mock Service didn't receive any request. But when I actually check the server logs (ServiceMix 4.2), I can see that actually the server has sent the request and even SOAP UI has responded according to the configured Mock Service. I don't have any clue about SOAP UI internals but it seems the test case execution flow is not correctly informed even though the Mock Service has responded, so the execution waits infinitely. In the concrete scenario where I have attached all the logs, even the next Mock Service has replied but the test case is still stuck on the previous one. Jetty log also confirms that next Mock Service was up.
I have attached all the logs and a screenshot of SOAP UI when it was stuck on the aforementioned Mock Service.
Please excuse me if the above description doesn't clearly explain the problem, I would be happy to provide any further clarification. Can you explain what might be happening ? Is this due to a bug in SOAP UI ?
Thank you very much in advance.
Nandana
I am using SOAP UI 4.0.0 for testing an integration project with several several Web Services. I am facing a strange behavior which happens randomly in one of our test cases. The test case (attached) has several steps including few SOAP requests and Mock services.
When I execute it, sometimes test case get stuck in some Mock Services as if the Mock Service didn't receive any request. But when I actually check the server logs (ServiceMix 4.2), I can see that actually the server has sent the request and even SOAP UI has responded according to the configured Mock Service. I don't have any clue about SOAP UI internals but it seems the test case execution flow is not correctly informed even though the Mock Service has responded, so the execution waits infinitely. In the concrete scenario where I have attached all the logs, even the next Mock Service has replied but the test case is still stuck on the previous one. Jetty log also confirms that next Mock Service was up.
I have attached all the logs and a screenshot of SOAP UI when it was stuck on the aforementioned Mock Service.
Please excuse me if the above description doesn't clearly explain the problem, I would be happy to provide any further clarification. Can you explain what might be happening ? Is this due to a bug in SOAP UI ?
Thank you very much in advance.
Nandana
