Browser support: run Playwright tests in Charlie devboxes
Charlie can now use a real browser in his devbox via Playwright. That means he can run browser-based end-to-end tests and validate UI flows before he opens a PR.
What’s new
- Playwright + browser dependencies are available in Charlie devboxes.
- Charlie can run your Playwright E2E suite as part of verification and fix failures end-to-end (not just unit tests).
- When a failure is visual/layout-related, he can reproduce it in the browser and include screenshots in the write-up.
Why it matters
- Many regressions only show up in the browser. Now Charlie can “see what you’d see” and iterate quickly.
- Faster reviews: fewer back-and-forth cycles asking for someone to run E2E locally.
- Higher confidence shipping changes that touch CSS, routing, auth, and critical user flows.
How to try it
In a PR/issue/slack thread, ask:
Run the Playwright E2E suite (
bun run test:e2e/playwright test). If anything fails, fix it and include the failing test name + a screenshot of the failure state.