I’m trying to migrate my load tests project to Gatling 3.0.2.
And I cannot think of a way to wait for responses on websocket in my specific case.
Here’s what I’ve got:
I’m sending some request, and as a result I receive several messages:
- Several messages indicating progress - number of these messages is not fixed and cannot be predicted in any way (as is depends among other things on current load on server etc.)
- A resulting message that I actually need.
So i thought I need to set a check which would match message #2 and have some reasonable timeout (like in 2.3.1).
But it always fails when the 1st of messages #1 is received.
Also there are other messages coming from time to time from the server not related at all to any requests i send, that could also come in between my request and response.
I could not think of any way to circumvent this limitation.
Or maybe I’m doing it wrong?