Property reset of TestRequest on TimeOut
Hello, I am using a Test Suite in SoapUI Pro 4.5.1 (4.5.2 shows same behaviour). Scenario: I am reading properties from a excel based data source, create a TestRequest with the properties and wri...
Forum Discussion
Hello,
unfortunately not. I simply face the problem that the response object isn't reset/deleted in case of "SoapUI Timeout".
Maybe this is a missing fact for your research. The timeout is triggered by SoapUI not the Webservice.
My SoapUI is set to 60 sec. To force and test this in my case I set the timeout in the Test Request step to 4 sec. This leads to the "-> java.net.SocketTimeoutException: Read timed out".
I again slightly adapted your code as I don't want the whole response in an excel cell.
And this still returns OK when I experience the above SocketTimeoutException.
So either this is a bug or I need another object/message/property where the TimeoutException for this test step is stored to be read out.
Best regards
unfortunately not. I simply face the problem that the response object isn't reset/deleted in case of "SoapUI Timeout".
Maybe this is a missing fact for your research. The timeout is triggered by SoapUI not the Webservice.
My SoapUI is set to 60 sec. To force and test this in my case I set the timeout in the Test Request step to 4 sec. This leads to the "-> java.net.SocketTimeoutException: Read timed out".
I again slightly adapted your code as I don't want the whole response in an excel cell.
def resp = testRunner.testCase.testSteps[ "Test Request" ].testRequest.response
def val = ( resp?.statusCode == 200 ) ? "OK" : "TIMEOUT"
testRunner.testCase.testSteps["DataSink"].setPropertyValue("Status", val);
And this still returns OK when I experience the above SocketTimeoutException.
So either this is a bug or I need another object/message/property where the TimeoutException for this test step is stored to be read out.
Best regards
