fake-summoner-server

To test socket.io server connectivity and broadcast events, use a fake server-side harness that simulates an actual socket.io client connection, enabling validation of both RPC responses and server broadcasts deterministically without real clients.

A fake CLI protocol stream simulates CLI and Claude protocol segments, emitting assistant, result, and control request events into the server to validate initialization workflows and tool permission flows during integration testing.

Verify session management and channel resume behavior by simulating multiple connected windows, driving initialize and launch segments, and asserting multi-layer side effects including store and DB persistence across simulated restarts.

Yes, you can test in-memory filesystem and git services during server-side integration tests by injecting fake services through a test DI container, allowing deterministic verification of filesystem and git side effects.

The best way to validate CLI stdin and control response handling is by driving fake protocol segments through a test DI container, then asserting multi-layer side effects across simulated stdin inputs and control response outputs.

You need a fake summoner for server-side testing when integration tests become slow or brittle, requiring realistic socket.io communication, simulated protocol streams, and in-memory filesystem behaviors to run deterministically.