1. 9
  1.  

  2. 2

    That’s what the TAP is for I see golang uses json for this purpose, so writing tap(universal) to json(golang specific) converter would allow using the same test harness.

    1. 2

      It’s become a bit of a best practice in Go to implement server protocols rather than mocking clients.

      Um, has it? You see it sometimes but I wouldn’t say frequently.