Problem
There are zero end-to-end tests. Unit tests cover individual modules but don't verify the full user journey works.
Proposed solution
Add one Playwright test covering the happy path:
- Start
mcpplay demo as a subprocess
- Wait for the server to be ready on
localhost:8321
- Open the browser to the UI
- Verify the tool list loads (sidebar shows tools)
- Click on a tool (e.g.,
echo)
- Fill in the form (type a message)
- Click Execute
- Verify the result appears in the result panel
- Verify a timeline entry was created
This single test covers: CLI startup, proxy connection, WebSocket communication, form rendering, tool execution, result display, and timeline recording.
Alternatives considered
Cypress or Puppeteer instead of Playwright. Playwright is the standard for modern E2E testing.
Problem
There are zero end-to-end tests. Unit tests cover individual modules but don't verify the full user journey works.
Proposed solution
Add one Playwright test covering the happy path:
mcpplay demoas a subprocesslocalhost:8321echo)This single test covers: CLI startup, proxy connection, WebSocket communication, form rendering, tool execution, result display, and timeline recording.
Alternatives considered
Cypress or Puppeteer instead of Playwright. Playwright is the standard for modern E2E testing.