A Question of Test Quality

We start by implementing a better work-around for socket.io’s lack of clean shut-down, then move into test-driving our network abstraction. We implement the connect() method, but the test is poor quality: it passes regardless of whether the code actually works. How can we check if the socket actually connected?

  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