All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
1.2.0 - 2023-06-10
- Added new
connect
action to provide greater control over WS connection during the scenario flow.
- Fixed bug disconnecting all sockets when forcing a new connection.
- The connection to the Socket.IO server will be made only when needed instead of during staging phase for the scenario.
- Instead of tracking the Websocket messages with code 0 in the Summary of an execution it will now appear as 101.
- Deprecates
scenario.flow.*.acknowledge.data
. Usescenario.flow.*.acknowledge.data
instead. - Deprecates
scenario.flow.*.emit.channel
. Equivalent to the first array element forscenario.flow.*.emit
. - Deprecates
scenario.flow.*.emit.data
. Equivalent to the second array element forscenario.flow.*.emit
. - Deprecates
scenario.flow.*.beforeRequest
. Usescenario.flow.*.connect
instead to establish any new connection to server. For everything else use a standalonescenario.flow.*.function
action. - Deprecates
scenario.flow.*.response.data
. Usescenario.flow.*.response.args
instead. - Deprecates
scenario.flow.*.reconnect
. Instead usescenario.flow.*.connect
to establish a new connection to server.
1.1.2 - 2021-08-29
- Compatability with Artillery v1.7+
1.1.1 - 2021-08-28
- Socket.IO v4 as a compatible version.
1.1.0 - 2021-08-28
- Bug capturing json value. By @gruffT
- Reconnect to close all the sockets and force reconnection by the client. By @gruffT
- Support to validate any event with any amount of exact arguments from the
response
with the newon
+args
option. - Support for the
response
validator to use thematch
API. - Support for configuring the Socket.IO client options under
config.engines.socketio-v3
acknowledge.args
as an alias ofacknowledge.data
. This is used to match the exact params of the ack function.