How do you test a WebSocket application?

Expected Interview Answer

Step-by-Step Explanation

1. Step 1

   Unit test with a mocked socket

   Replace the WebSocket with a fake that lets you assert outgoing frames and simulate incoming messages, errors, and close events.

2. Step 2

   Integration test a real server

   Start an actual WebSocket server and connect a genuine client to verify handshake, auth, message flow, and protocol conformance.

3. Step 3

   Test reconnection and backoff

   Force disconnects and confirm the client retries with exponential backoff and restores subscriptions and state.

4. Step 4

   End-to-end in the browser

   Use Playwright or Cypress to drive the UI and confirm real-time updates render correctly to the user.

5. Step 5

   Load and soak test

   Open thousands of concurrent connections to measure latency, backpressure, and memory growth over time.

Code Example

const { WebSocketServer } = require('ws')
const WebSocket = require('ws')

test('echoes a message back to the client', (done) => {
  const server = new WebSocketServer({ port: 0 })
  server.on('connection', (socket) => {
    socket.on('message', (data) => socket.send(data))
  })

  const { port } = server.address()
  const client = new WebSocket(`ws://localhost:${port}`)

  client.on('open', () => client.send('ping'))
  client.on('message', (msg) => {
    expect(msg.toString()).toBe('ping')
    client.close()
    server.close(done)
  })
})

Follow-up Questions

• How would you mock a WebSocket in a unit test?
• How do you load-test thousands of concurrent connections?
• How do you test reconnection with exponential backoff?
• How do you assert message ordering guarantees?
• What tools help debug a live WebSocket connection?