Forum Discussion
Magnus
17 years agoOccasional Contributor
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.
/Magnus
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.
/Magnus