Use preinstalled Chrome for CI browser tests #25

Merged

lost-rob0t merged 2 commits from fix/ci-runner-chrome into main

2026-08-19 12:08:42 +00:00

lost-rob0t commented

2026-08-19 12:07:03 +00:00

(Migrated from github.com)

Summary

Unblocks the browser E2E gate without weakening it.

Two otherwise-green PR runs are currently hanging in npx playwright install --with-deps chromium, after format, lint, typecheck, boundary/static checks, unit tests, build, and artifact validation all pass. The GitHub-hosted Ubuntu image already includes stable Google Chrome, and Playwright supports driving the installed chrome channel directly.

keep local/default Playwright on bundled Chromium behavior;
use channel: "chrome" only under CI;
replace the network browser download with an explicit google-chrome --version runner validation;
continue running the complete Playwright suite as a required CI step.

This changes the CI browser binary, not the test coverage or merge gate. If Chrome is missing from the runner image, CI fails immediately and clearly instead of silently skipping browser tests.

## Summary Unblocks the browser E2E gate without weakening it. Two otherwise-green PR runs are currently hanging in `npx playwright install --with-deps chromium`, after format, lint, typecheck, boundary/static checks, unit tests, build, and artifact validation all pass. The GitHub-hosted Ubuntu image already includes stable Google Chrome, and Playwright supports driving the installed `chrome` channel directly. - keep local/default Playwright on bundled Chromium behavior; - use `channel: "chrome"` only under `CI`; - replace the network browser download with an explicit `google-chrome --version` runner validation; - continue running the complete Playwright suite as a required CI step. This changes the CI browser binary, not the test coverage or merge gate. If Chrome is missing from the runner image, CI fails immediately and clearly instead of silently skipping browser tests.