Repository navigation
feat: add two-tier e2e tests for daemon pipeline #24
Description
Context
All 57 tests are unit tests with mocked data. Nothing validates the full pipeline: WebSocket connection → DevTools bridge → ComponentTree → Profiler → IPC → response. Protocol-level regressions are invisible. The root package.json already has "test:e2e" pointing to a non-existent e2e-tests package.
Plan
Two test tiers in packages/e2e-tests/:
| Tier | Trigger | What | Speed |
|---|---|---|---|
| Protocol | Every PR | Fake WS backend → real daemon → IPC responses | ~2-3s |
| Browser | Main only | Playwright + real Vite app in headless Chromium | ~15-20s |
Protocol tests (every PR)
- Fake React DevTools backend connects via WebSocket, sends real operations arrays + profiling data
- Tests: status, get-tree, find, count, get-component (with inspect response), profiling flow, disconnect cleanup
Browser tests (release only)
- Playwright opens the real Vite example app in headless Chromium
- Tests: real connection, real tree, real find, real inspect, real profiling with UI interaction
CI
build.yml: add protocol e2e after unit tests- New
e2e.yml: browser tests on pushes to main only
Activity
piotrski commentedon Feb 14, 2026
Resolved — protocol-level e2e tests were added in #25 and expanded in #27. Closing as the packages/e2e-tests suite now covers daemon lifecycle, component tree, profiling, CLI commands, and connection health.
feat: add protocol-level e2e tests (#24)