Forum Discussion
mermet
17 years agoOccasional Contributor
Hi, I have also a similar requirement, as my Test Cases all use Mock Responses (asynchroneous Notification Process).
I have seen that the MockService Runner is accepting a port option. Could possibly the MockResponse listening Port be configured to be unique for each LoadTest Thread ?
This unique port value would need to be generated / known earlier in the Test Case in order to:
1) Tell the target Application on which port to invoke the Mock Response for that Thread
2) Start the Mock Response on that port value for current Thread.
Ultimately, as the Mock Responses are listening on different port numbers, there will be no need for Mock Responses to be synchronized.
Regards.
I have seen that the MockService Runner is accepting a port option. Could possibly the MockResponse listening Port be configured to be unique for each LoadTest Thread ?
This unique port value would need to be generated / known earlier in the Test Case in order to:
1) Tell the target Application on which port to invoke the Mock Response for that Thread
2) Start the Mock Response on that port value for current Thread.
Ultimately, as the Mock Responses are listening on different port numbers, there will be no need for Mock Responses to be synchronized.
Regards.