From a453b74b04fabc1f1ced4efb237429ec933269da Mon Sep 17 00:00:00 2001 From: Ilia Denisov Date: Sat, 23 May 2026 18:24:55 +0200 Subject: [PATCH] test(ui): assert relative manifest start_url in the PWA spec The single-origin manifest now uses relative URLs (`start_url: "./"`) so it stays base-agnostic under `/` and `/game/`. Update the PWA spec to assert the relative value instead of the old absolute `/`. Co-Authored-By: Claude Opus 4.7 (1M context) --- ui/frontend/tests/pwa/pwa.spec.ts | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ui/frontend/tests/pwa/pwa.spec.ts b/ui/frontend/tests/pwa/pwa.spec.ts index aaf7fa6..d24e35b 100644 --- a/ui/frontend/tests/pwa/pwa.spec.ts +++ b/ui/frontend/tests/pwa/pwa.spec.ts @@ -18,7 +18,10 @@ test.describe("PWA", () => { .get(href!) .then((r) => r.json()); expect(manifest.name).toBe("Galaxy"); - expect(manifest.start_url).toBe("/"); + // Relative so the manifest is base-agnostic: served under the app + // base (`/` at the root, `/game/` in the single-origin deploy) it + // resolves to the app root either way. + expect(manifest.start_url).toBe("./"); expect(manifest.display).toBe("standalone"); const sizes = (manifest.icons as { sizes: string }[]).map((i) => i.sizes); expect(sizes).toContain("192x192");