1. Recorded Live
  2. Chapter 79
  3. E593: Connect Null Client
CH79 / E593|Disentangling Business Logic|Mon, 12 Feb ’18

Connect Null Client

As we continue converting our real-time server’s logic tests to work independently of the network, we run into a snag: our server checks that a client is connected before sending messages related to that client. But our new test doesn’t actually establish any connections. How can we solve this problem? More importantly, how can we make it clean?

  1. E585Remove the Network Complexity

    Mon, 15 Jan ’18

  2. E586Extract the Instantiation

    Wed, 17 Jan ’18

  3. E587From Child to Sibling

    Mon, 22 Jan ’18

  4. E588A Different Kind of Stub

    Wed, 24 Jan ’18

  5. E589A Null Real-Time Server

    Mon, 29 Jan ’18

  6. E590The Wrong ID

    Wed, 31 Jan ’18

  7. E591getLastSentMessage()

    Mon, 5 Feb ’18

  8. E592A Test Without a Network

    Wed, 7 Feb ’18

  9. E593Connect Null Client

    Mon, 12 Feb ’18

  10. E594Null Socket

    Wed, 14 Feb ’18

  11. E595Emit an Event

    Mon, 19 Feb ’18

  12. E596Translating Tests

    Wed, 21 Feb ’18

  13. E597Double Timeout

    Mon, 26 Feb ’18

  14. E598Look How Much Simpler It Is

    Wed, 28 Feb ’18

  15. E599I Love Deleting Code

    Mon, 5 Mar ’18