According to the documentation:
Gatling currently only support one check at a time per websocket.
If I set a check directly onto the websocket I could listen on every incoming messages but I cannot initiate a new sendTest with a check as it overrides the first one.
If I create a new check with sendText I cannot listen on other pushed messages from the server.
So as it is now it makes almost impossible to test a complex websocket application with request/response and pushed messages from the server especially when those requests depend on some pushed messages.
I would like to implement a cometd layer on top of the websocket module. But the current implementation prevents me to be able to implement publish/subscribe functionality as I cannot handle properly pushed messages.
The scenarios is the following:
I subscribe to a topic in the server which is going to push messages in regular time period. I would like to process those messages like saving data to session to drive synchronous request/responses with wsAwait.
I send commands based on the pushed messages and check the response.
Is there any way how I could handle request/response (wsAwait) and pushed messages (wsListen) paralel way?