diff options
| author | Aman Kumar <145339995+amankumarsingh77@users.noreply.github.com> | 2026-06-21 00:46:44 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-06-21 00:46:44 +0530 |
| commit | da5d31af999b728c31ab0169373531cab4543f0c (patch) | |
| tree | 5d350ad1428ff332372a9c724ac46c964d8ca477 /test/manual/e2e-test.ts | |
| parent | 8db684d43366d335760e106eae39a74376bd7640 (diff) | |
release: v0.6.0 — per-tab isolation, Unix socket daemon, on-demand init (#6)
* feat: Unix socket daemon with auto-reconnect for persistent Chrome CDP
Eliminates the 'Allow Remote Debugging' Chrome prompt that appeared on
every pi session by multiplexing pi instances through a single persistent
daemon process.
Key additions:
- Unix socket IPC (net.createServer + readline JSON framing)
- CdpBridge with ID multiplexer + event router
- DaemonTransport implementing CdpTransport interface
- Auto-spawn with ensureDaemon() (lazy, checks socket)
Fixes since initial implementation:
- Bridge auto-reconnects to Chrome with exponential backoff (1s-60s).
Previously the bridge tried once at startup and permanently failed
if Chrome wasn't ready — causing 'Chrome not connected' on every
browser tool call.
- Daemon spawn uses project-local tsx binary instead of global --import
flag, fixing silent spawn failure (ERR_MODULE_NOT_FOUND).
- Stale ctx crash: persistState in onOwnershipChange wrapped in
try/catch to prevent CDP event consumer crashes.
49 test assertions across 4 test files. Zero TypeScript errors.
* feat: on-demand browser initialization
Browser daemon no longer auto-starts on session_start. Instead:
- session_start creates the client lazily but does NOT connect or spawn
the daemon. Zero Chrome prompts for non-browser pi sessions.
- Browser tool wrapper checks for daemon socket before each call.
Socket missing → clear error: 'Run /browser-setup first'.
Socket exists → proceeds silently (daemon already running).
- /browser-setup is the explicit, one-time init point. It spawns
the daemon and connects to Chrome only when the user opts in.
- SKILL.md updated with Connection Setup instructions telling agents
to direct users to /browser-setup when socket is missing.
* fix: checkChromeRunning on macOS — match by substring not exact
ps -A -o comm= returns full executable paths on modern macOS
(e.g. /Applications/Google Chrome.app/Contents/MacOS/Google Chrome),
not the basename. The old exact-match check (browserProcesses.includes(l))
never matched, causing false 'No browser instance running' errors.
Changed to substring includes() with helper/renderer/crashpad filtering.
* feat: browser_setup as agent-callable tool
The agent can now self-recover from 'Browser harness not initialized'
errors by calling browser_setup directly — no user mediation needed.
- Extracted shared performSetup() from the slash command into setup.ts
- Created src/domains/setup.ts with ensureAlive:false to bypass the
socket guard (this tool IS the setup, can't require itself)
- Registered browser_setup in the tool registry
- Updated SKILL.md: agent calls browser_setup directly, not ask user
- Removed stale test/manual/spawn-test.ts
* release: v0.6.0 — per-tab isolation, Unix socket daemon, on-demand init
Diffstat (limited to 'test/manual/e2e-test.ts')
| -rw-r--r-- | test/manual/e2e-test.ts | 163 |
1 files changed, 163 insertions, 0 deletions
diff --git a/test/manual/e2e-test.ts b/test/manual/e2e-test.ts new file mode 100644 index 0000000..963efaf --- /dev/null +++ b/test/manual/e2e-test.ts @@ -0,0 +1,163 @@ +/** + * End-to-end integration test: full daemon pipeline. + * + * Starts the daemon (IpcServer + CdpBridge), connects via DaemonTransport, + * exercises the full CDP request/response/event lifecycle. + * + * Run: npx tsx test/manual/e2e-test.ts + */ +import { createIpcServer } from "../../src/daemon/server"; +import { createCdpBridge, type SendToClient } from "../../src/daemon/bridge"; +import { createDaemonTransport } from "../../src/cdp/daemon-transport"; +import { DAEMON_SOCKET_PATH } from "../../src/daemon/protocol"; +import type { WireRequest } from "../../src/daemon/protocol"; +import { unlinkSync } from "node:fs"; + +let passed = 0; +let failed = 0; +const check = (cond: boolean, label: string) => { + if (cond) { passed++; console.log(` ✓ ${label}`); } + else { failed++; console.error(` ✗ ${label}`); } +}; + +async function main() { + // Clean up stale socket + try { unlinkSync(DAEMON_SOCKET_PATH); } catch {} + + // ── Start daemon ─────────────────────────────────────────────────────── + console.log("Starting daemon (IpcServer + CdpBridge)..."); + const ipcServer = createIpcServer(); + const cdpBridge = createCdpBridge(); + + // Wire IpcServer ↔ CdpBridge + ipcServer.onMessage((msg, client) => { + if (msg.type !== "request") return; + const send: SendToClient = (cid, resp) => ipcServer.send(cid, resp); + cdpBridge.handleRequest(msg, client.id, send); + }); + + cdpBridge.onEvent((event, targetClientIds) => { + for (const cid of targetClientIds) ipcServer.send(cid, event); + }); + + ipcServer.onDisconnect((client) => cdpBridge.removeClient(client.id)); + + await ipcServer.start(); + console.log("Daemon started ✓"); + + // The bridge will try to connect to Chrome — might fail, that's ok for + // this test. We'll simulate CDP responses from the server side. + + // ── Connect pi client via DaemonTransport ────────────────────────────── + console.log("\nConnecting pi client (DaemonTransport)..."); + const transport = createDaemonTransport("pi-e2e-test"); + + const connectResult = await transport.connect(""); + check(connectResult.success, `Client connect: ${connectResult.success ? "ok" : connectResult.error.message}`); + check(transport.state() === "open", "Transport state is open"); + + // ── Test 1: Request → simulated CDP response ─────────────────────────── + // The IpcServer's onMessage handler forwards requests to the bridge. + // The bridge tries to send to Chrome (which may be down). For this test, + // we intercept at the IpcServer level and simulate CDP responses. + + // Override the message handler to simulate CDP responses directly. + let rawRequests: WireRequest[] = []; + ipcServer.onMessage((msg, client) => { + if (msg.type === "request") { + rawRequests.push(msg); + // Simulate a CDP success response + ipcServer.send(client.id, { + type: "response", + id: msg.id, + result: { simulated: true, method: msg.method }, + }); + } + }); + + const res1 = await transport.request("Page.navigate", { url: "https://example.com" }); + check(res1.success, "CDP request succeeded"); + if (res1.success) { + const d = res1.data as any; + check(d?.simulated === true, "Response contains simulated flag"); + check(d?.method === "Page.navigate", "Response echoes method"); + } + check(rawRequests.length === 1, "Server received exactly 1 request"); + check(rawRequests[0]!.method === "Page.navigate", "Correct method forwarded"); + + // ── Test 2: Request with sessionId ───────────────────────────────────── + rawRequests.length = 0; + const res2 = await transport.request("Runtime.evaluate", { expression: "1+1" }, { sessionId: "session-abc" }); + check(res2.success, "Session-scoped request succeeded"); + check(rawRequests[0]?.sessionId === "session-abc", "SessionId forwarded correctly"); + + // ── Test 3: Multiple parallel requests ───────────────────────────────── + rawRequests.length = 0; + const [r3a, r3b, r3c] = await Promise.all([ + transport.request("Target.getTargets", {}), + transport.request("Browser.getVersion", {}), + transport.request("Page.captureScreenshot", {}), + ]); + check(r3a.success && r3b.success && r3c.success, "All 3 parallel requests succeeded"); + check(rawRequests.length === 3, "Server received all 3 requests"); + + // ── Test 4: Events ───────────────────────────────────────────────────── + const eventPromise = new Promise<string | null>((resolve) => { + const timeout = setTimeout(() => resolve(null), 2000); + (async () => { + for await (const evt of transport.events()) { + clearTimeout(timeout); + resolve(evt.method); + break; + } + })(); + }); + + // Simulate a CDP event broadcast from the daemon + ipcServer.broadcast({ + type: "event", + method: "Target.targetCreated", + params: { targetInfo: { type: "page", targetId: "e2e-test-target" } }, + }); + + const eventMethod = await eventPromise; + check(eventMethod === "Target.targetCreated", `Event received: ${eventMethod ?? "TIMEOUT"}`); + + // ── Test 5: Session persistence (detach simulation) ──────────────────── + // Simulate a session shutdown: close the transport, then reconnect. + // The transport.close() sends deregister, server cleans up. + await transport.close(); + check(transport.state() === "closed", "Transport closed"); + + // Small delay for server cleanup + await new Promise(r => setTimeout(r, 500)); + + // Reconnect — simulates next pi session + const reconnectResult = await transport.connect(""); + check(reconnectResult.success, "Transport reconnected (simulated session restart)"); + + // Send a request through the reconnected transport + const res4 = await transport.request("Target.getTargets", {}); + check(res4.success, "Request after reconnect succeeded"); + check(transport.state() === "open", "Transport state is open after reconnect"); + + // ── Test 6: Server-side client count ─────────────────────────────────── + check(ipcServer.clientCount() === 1, "Server reports 1 connected client"); + + // ── Test 7: Client disconnect cleanup ────────────────────────────────── + await transport.close(); + await new Promise(r => setTimeout(r, 500)); + check(ipcServer.clientCount() === 0, "Server reports 0 clients after disconnect"); + + // ── Cleanup ──────────────────────────────────────────────────────────── + await ipcServer.stop(); + console.log("\nDaemon stopped ✓"); + + console.log(`\n${passed} passed, ${failed} failed`); + process.exit(failed > 0 ? 1 : 0); +} + +main().catch((e) => { + console.error("E2E test failed:", e); + process.exit(1); +}); |
