1. Recorded Live
  2. Chapter 53
  3. E392: This Kills the Browser
CH53 / E392|A Network Test Harness|Wed, 9 Mar ’16

This Kills the Browser

We modify our waitForServerDisconnect() test harness call to check whether a socket has been closed and, if it hasn’t, to wait for the disconnect event before returning. After struggling with socket.io’s miserable documentation, we figure out something that works... almost. The event doesn’t fire and the browser times out. What could be wrong?

  1. E386Hang Ten

    Wed, 17 Feb ’16

  2. E387A Question of Test Quality

    Mon, 22 Feb ’16

  3. E388The AJAX Back-Channel

    Wed, 24 Feb ’16

  4. E389Connection Query

    Mon, 29 Feb ’16

  5. E390Show Some ID

    Wed, 2 Mar ’16

  6. E391Racing to Disconnect

    Mon, 7 Mar ’16

  7. E392This Kills the Browser

    Wed, 9 Mar ’16

  8. E393Pointing the Way

    Mon, 14 Mar ’16

  9. E394An Eventful Race

    Wed, 16 Mar ’16