Consider supporting connection delays about jest-websocket-mock HOT 3 CLOSED

Hi @marcospassos !

What exactly are you trying to test?

When testing connection timeouts, it's usually better to mock timers rather than artificially introduce delays, as they can make tests slow and flakey.

(For instance, jest will kill tests if they take longer than 5 seconds - that makes it impossible to test reconnection or timeout logics without mocking out the timers.)

from jest-websocket-mock.

Hi @marcospassos !

I think that a graceful solution for this could be to add a autoConnect option to WSOptions in the constructor that defaults to true.

We could then move this block to a separate connect function: https://github.com/romgain/jest-websocket-mock/blob/master/src/websocket.ts#L48-L60 , that would be called automatically when autoConnect is true.

You're use case would then be achieved like this:

const server = new WS("ws://localhost:1234", { autoConnect: false });

expect(client.readyState).toBe(WebSocket.CONNECTING);

setTimeout(() => server.connect(), 10000);

// 10 seconds later...
await server.connected;

What do you think?

Would you be open to sending a PR that adds this?

from jest-websocket-mock.

Closing for now, but feel free to reopen if you have more feedback/questions!

from jest-websocket-mock.