Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

make test-webkit runs the drag specs in WebKit against the test stack

Browse Source 
WebKit takes *.localhost to loopback through GLib and ignores /etc/hosts, so
the container shares Traefik's network namespace. The webkit project only
exists with PLAYWRIGHT_WEBKIT=1, so test-frontend stays Chromium only.
This commit is contained in:
stroblme
2026-10-15 16:15:39 +02:00
parent fbd886f7a7
commit 146ab72c17
3 changed files with 32 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
development.md
+8 -3
View File
@@ -144,10 +144,15 @@ the Traefik container's address twice, with `--add-host` and with `HOST_RESOLVER
because Chromium pins `*.localhost` to loopback whatever `/etc/hosts` says. Narrow a run with
`make test-frontend PLAYWRIGHT_ARGS="--grep flows"`.
`make test-webkit` runs the drag specs in WebKit against the same stack. WebKit takes
`*.localhost` to loopback through GLib and ignores `/etc/hosts`, so that container shares
Traefik's network namespace, where loopback is Traefik. Playwright's Linux WebKit reads a
`writing-mode: vertical-lr` range across, so a vertical slider's geometry is not asserted there.
The specs are `frontend/tests/*.spec.ts`; `playwright.config.ts` defines `setup` →
`chromium` and `mobile`. `auth.setup.ts` logs in once into `playwright/.auth/user.json`,
which both browser projects reuse; `mobile` runs `mobile.spec.ts` only, on a Pixel 5 at
393px.
`chromium` and `mobile`, plus `webkit` when `PLAYWRIGHT_WEBKIT=1` is set. `auth.setup.ts` logs
in once into `playwright/.auth/user.json`, which the browser projects reuse; `mobile` runs
`mobile.spec.ts` only, on a Pixel 5 at 393px.
Both origins come from `PLAYWRIGHT_BASE_URL` and `PLAYWRIGHT_API_URL`, deliberately never
from `VITE_API_URL` — that one belongs to the app build and in a deployment checkout it