Sorry, this video is for subscribers only.

Click here to subscribe!

Re-Port-ing

We’re adding a little method for getting the port of our RealTimeConnection. This opens up a can of worms: how do we want the port to reported after the connection’s been closed? How does that interact with our Null connection? How can we eliminate duplication in our Null connection tests? We take each question in turn.

  1. E456An Alternative to Test Doubles

    Wed, 19 Oct ’16
  2. E457A Null Connection

    Mon, 24 Oct ’16
  3. E458State in the Union

    Wed, 26 Oct ’16
  4. E459Re-Port-ing

    Mon, 31 Oct ’16
  5. E460getLastSentPointerLocation()

    Wed, 2 Nov ’16
  6. E461Trigger the Network Event

    Mon, 7 Nov ’16
  7. E462No More Test Double

    Wed, 9 Nov ’16
  8. E463Null Socket

    Mon, 14 Nov ’16
  9. E464Managing Complexity

    Wed, 16 Nov ’16
  10. E465Testing Concurrency

    Mon, 21 Nov ’16
  11. E466Event Handling

    Wed, 23 Nov ’16
  12. E467Test the Null

    Mon, 28 Nov ’16