Artillery: Websocket responses support

[SamDecrock]

Hi,

I'm looking for a way to implement websocket message testing. Other than JMeter I can't find any testing tool.

Do you have an estimate as to when websocket response parsing/checking will be implemented?

Thanks,
Sam

[hassy]

Not planned for a specific release at this point, but PRs are always welcome. :)

Both HTTP and Socket.io engines have support for it - copying the relevant bits into the WebSocket engine should be pretty straightforward.

[MosayebG]

In artillery-core and engine_socketio.js i change this lines and now callback works for me:

// No return data is expected, so emit without a listener
socketio.emit(outgoing.channel, outgoing.data, function(result){

    markEndTime(ee, context, startedAt);
        return callback(null, context);
});

I forked artillery-core here by editing this

[etwillbefine]

What is the status here?
Doesnt seem to be that straightforward if no one cares about for 2 years now..

What if we need to parse responses to ensure following calls can use these variables. Like a subscription id or something similar. Do I miss something here?

[tarikki]

Any updates on this?

I need to grab a unique value after the connection is made to make subsequent requests, for this I would need response parsing.

[michyliao]

Any update?