WebSocket testing labUse the chat as a real test target
Open the page in two browser windows, keep DevTools open in one, and verify the connection and message flow instead of testing only the visible UI.
What to test
- Handshake. Confirm the WebSocket upgrade succeeds and the connection remains open.
- Message flow. Send text and an image from window A and verify the same payload reaches window B and the sender.
- Presence. Open and close extra windows and check that the online count follows active connections.
- Reconnect. Interrupt the socket or network, observe the close, then use Reconnect and verify a clean new connection.
- Boundaries. Try empty input, long messages, Unicode, image size/type limits, rapid sends and several clients at once.
Where to look
DevTools → Network → WSConnection URL, request/response headers and the opening handshake.
Messages / FramesOutgoing and incoming payloads, order, timing, image payload size and unexpected duplicates.
ConsoleClient-side connection errors, parsing failures and reconnect issues.
Server logsConnection IDs, room membership, broadcasts, disconnects and correlation between clients.