You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To be perfectly blunt, no. Node uses an event loop, k6 uses VU iterations. An API like this would make no sense for us, like I keep saying every time someone asks for this.
The websocket API is different because it starts its own event loop inside of a VU iteration.
Browsers and NodeJS provide a Timers API.
k6
could also provide ak6/timers
API.The WebSocket API provides the Socket.setTimeout and Socket.setInterval methods to delay a function call while the WebSocket connection is open.
May users want to use the
k6/timers
API for non-WebSocket tests as well?If yes, the
k6/timers
API in conjunction with an API for the WebSocket connection status would deprecate the Socket.setTimeout and Socket.setInterval.The text was updated successfully, but these errors were encountered: