Repository navigation
End-to-end tests run in Chromium only #808
Description
#550's browser criterion is unchecked because tests/e2e/playwright.config.js defines only chromium and chromium-multisite, and CI installs only Chromium, so a Firefox or Safari regression in the admin bar, the post-lock notice or the stale-screen banner would ship unseen.
Playwright already bundles Firefox and WebKit, so this is mostly config, but each browser adds a full e2e run to CI, which already takes several minutes (#593).
Tasks
-
firefoxandwebkitprojects inplaywright.config.js, besidechromium - Install those browsers in
.github/workflows/e2e.ymland add them to the job'smatrix.project - Decide when they run: on every pull request, or only on
mainand a schedule to keep pull request CI fast - Fix or mark any spec that fails only in one browser, with the reason
Part of #550.
Activity
i-am-chitti commentedon Oct 12, 2026
I was thinking to pick it up. Chromium already runs the full suite on every PR. Running all of it again in Firefox and WebKit would mostly re-test PHP through a different browser, since most of our specs check REST, Heartbeat payloads and list tables. The parts that could really break in one browser and not another are narrow: tab coalescing (Web Locks and BroadcastChannel), leader election on
visibilitychange, and the admin bar CSS.So I'd suggest doing it the way Gutenberg does:
firefoxandwebkitprojects that only run specs tagged@firefox/@webkitpresence-tab-coalescing,presence-stale-screen-coalescing,presence-active-posts-coalescing,presence-visibilityandpresence-admin-bar-contraste2e.yml, with the browser in the cache key so jobs don't restore each other's cachesThat keeps PR CI close to what it is now, so they can run on every PR rather than on a schedule.
@josephfusco What do you think?
josephfusco commentedon Oct 12, 2026
Sounds good, it's yours. The manual Safari, Firefox and Edge pass recorded on #550 covers the merge criterion.