Magnus
Occasional Contributor
Joined 18 years ago
User Profile
User Widgets
Contributions
Conditional Goto condition validation fails for subsequent mock responses
It seems like the Conditional Goto condition always validates towards the first request received by the mock response test step. When the same conditional goto step is reached the next time it does not validates towards the last mock response request.2.4KViews0likes1CommentRe: MockResponses listening on different ports in a Load Test
Hi Ole! That sounds great We really need this feature to be able to use soapui Pro to system test the web services application in our project. When have you planned for the next release? The one after 2.0. Regards, Magnus2.7KViews0likes0CommentsRe: MockResponses listening on different ports in a Load Test
Thanks for your answer! The idea with the session id I think is good if it could be implemented in the following way. Two new "variables" are introduced and associated with a Mock Response. One that contains the id (session id) and one that contains an XPath statement. When the thread that is responsible of receiving "asynchronous" requests receives a request, it uses the XPath statement to extract the id (session id) from any XML element or property that was received in the request and then dispatches the request to the MockResponse with the same id. It is important that the id in the MockResponse can be set by using the step type Property Transfer. This feature would be very good to have (is a must I would say) when load testing applications that are using the publish/subscribe mechanism or any applications that are sending out asynchronous events. /Magnus2.7KViews0likes0CommentsMockResponses listening on different ports in a Load Test
Hi, How can I achieve so that asynchronous requests that are received by Test Case instances in a Load Test is routed to the right test case instance? The test case consists for example of two steps. One request that is sent to the testing object. The testing object will responde to this request asynchronous at any time. The other step in the test case is a MockResponse that reveives the asynchronous request. This works just fine if all the requests in the Load Test are executed sequentially. But if they are executed concurrently "which they usually are in a load test" the asynchronous request could reach any test case instance since the MockResponse in all test cases are listening to the same port. How can this be solved? We tried to use a variable when defining the port in the MockResponse. But it was not possible. Any other suggestions? Regards, Magnus6.1KViews0likes7Comments