$ show ajhsu/chromecast-device-emulator
The Chromecast Device Emulator is a Node.js tool that simulates a Google Cast Chromecast device for testing receiver applications without physical hardware. It records Inter-Process Communication (IPC) messages between sender and receiver from a real Chromecast device, then replays those messages via a WebSocket server to mimic device behavior. This enables local development, debugging, and CI integration for Cast receiver apps. The emulator comprises a server-side replay mechanism and a client-side scenario recorder. The server (`src/index.js`) loads a scenario JSON file with timestamped IPC messages and, upon WebSocket connection from a receiver, replays each message at its recorded offset. The client recorder (`src/receiver-utils/scenario-recorder.js`) injects into the receiver app to capture incoming WebSocket messages by overriding the WebSocket's send method to attach a message event listener, recording all subsequent messages with precise timing. Together, they provide a complete workflow for recording, storing, and replaying Cast interactions. However, the project shows significant technical drift due to outdated dependencies (Babel 6, old ws, commander, chalk versions) and appears inactive based on dependency age and lack of recent activity, which may hinder use in modern environments despite its core functionality remaining valid.
The LLM identified 2 files worth highlighting for reuse:
This client-side script overrides the WebSocket's send method to capture incoming messages for scenario recording. It demonstrates a non-obvious technique of using a one-time event listener setup to record all subsequent messages without modifying application code. The component is self-contained (depends only on global WebSocket and window) and can be extracted for use in any WebSocket-based application to record messages for testing or replay.
The core emulator class that sets up a WebSocket server to replay recorded IPC messages at specified timestamps. It handles multiple simultaneous connections by independently scheduling message replays for each connection. While the pattern is standard, the implementation is clean, self-contained (depending only on ws, chalk, and a simple logger), and encapsulates the replay logic in a reusable manner. It could be adapted for testing other WebSocket-based protocols with minimal changes.