enso-test

Comprehensive live end-to-end test of the Enso platform. Tests infrastructure, backend, and frontend features in the browser with strict pass/fail criteria.

Prerequisites: Chrome MCP (Claude in Chrome) must be connected for Phase 4 browser tests. Enso services must be running (./restart.sh if not).

Approach: If any tests fail, list all failures with root causes and recommend specific fixes. The user can then enter plan mode to address issues before re-testing.

Phase 1 — Infrastructure Health

Verify all services are running. If any fail here, stop and tell the user to run ./restart.sh first.

1. Plugin server: curl -sf http://localhost:3001/health → must return {"ok":true}
2. Vite dev server: curl -sf -o /dev/null -w '%{http_code}' http://localhost:5173 → must be 200
3. Version endpoint: curl -sf http://localhost:3001/api/version → must return valid JSON with versionCode field
4. Action log: curl -sf "http://localhost:3001/api/action-log?count=5" → must return JSON array
5. WebSocket: Write a quick Node script to verify WS connection:

   node -e "
     const ws = new (require('ws'))('ws://localhost:3001/ws');
     ws.on('open', () => { console.log('WS_OK'); ws.close(); process.exit(0); });
     ws.on('error', (e) => { console.log('WS_FAIL:', e.message); process.exit(1); });
     setTimeout(() => { console.log('WS_TIMEOUT'); process.exit(1); }, 5000);
   "
   

   If ws module not available, skip this check with a note.

Record the current timestamp before proceeding — you'll use it in Phase 5 to filter new errors.

Phase 2 — Backend Unit Tests

Run the Vitest test suite:

npx vitest run --reporter=verbose 2>&1

Pass criteria: All tests pass (exit code 0). Report X/Y passed. If any fail, log the failure details but continue testing.

Phase 3 — TypeScript Compilation

Run both server and frontend type checks:

npx tsc -p tsconfig.server.json --noEmit 2>&1
npx tsc --noEmit 2>&1