- Production now runs from ~/freezmo-prod/current (release symlink) as a standalone server on :3207; releases are exported by scripts/deploy.sh, built and e2e-verified on a temp port, switched atomically, health- checked via the new /api/healthz (commit + build time) and rolled back automatically on failure. Last 5 releases kept; scripts/rollback.sh for manual rollback. Shared env + data live in ~/freezmo-prod/shared/ and are symlinked into every release (existing sync/push data migrated and verified identical). - Dev runs from ~/freezmo via freezmo-dev.service: next dev on :3217 (LAN only), its own build folder (.next-dev via NEXT_DIST_DIR), its own data (~/freezmo/.freezmo-dev), DEV badge, dev favicon/theme colour, "Freezmo Dev" PWA identity and never the production service worker. - /api/healthz + the Settings Details version row (short commit + build time). output: standalone in next.config (next start still works). - AGENTS.md documents the workflow rules: only dev updates during a task, temporary dirs/ports for test builds, and deploy-at-the-end as the only production path. README gains an Environments and deploy section. - Fix found by the rehearsal: lib/dev-mode.ts must not be a client module (a server component importing a constant from a "use client" module gets a truthy proxy, which baked dev metadata into production builds). - SW -> freezmo-v34. |
||
|---|---|---|
| .. | ||
| bubble-perf.mjs | ||
| bubbles-test.mjs | ||
| chat-test.mjs | ||
| freeze-loading-test.mjs | ||
| i18n-test.mjs | ||
| lib.mjs | ||
| mobile-test.mjs | ||
| model-compare.mjs | ||
| native-test.mjs | ||
| phase1-test.mjs | ||
| phase2-test.mjs | ||
| phase3-test.mjs | ||
| README.md | ||
| regression.mjs | ||
| review-test.mjs | ||
| run-all.mjs | ||
| wizard-test.mjs | ||
Browser suites
End-to-end checks for Freezmo, driven by Playwright against a running
production build. Everything lives in this repo (nothing in /tmp), so a
reboot cannot wipe the harness.
Requirements
- The app is running on
http://127.0.0.1:3207(systemctl --user start freezmo). - A Chromium build. The suites auto-detect the newest Playwright Chromium in
~/.cache/ms-playwright/; override withCHROME=/path/to/chrome. npm install(dev deps:playwright-core,axe-core).
Running
npm run build && systemctl --user restart freezmo # fresh build first
npm run test:e2e # every suite, in order
npm run test:e2e -- phase1 # only suites whose name contains "phase1"
Each suite prints PASS/FAIL lines and exits non-zero on failure; the runner
prints a per-suite summary at the end.
Suites
| Suite | Covers |
|---|---|
regression.mjs |
Library, deck card + menu, study feed to results, homework entry, desktop shell + settings/health panel. |
bubbles-test.mjs |
Ice-scene bubbles: stacking/layout contract, keyframes only transform+opacity, rise/sway/scale/fade phases, per-breakpoint counts (5/3/2), phone pacing, reduced motion, tab-hidden parking. |
mobile-test.mjs |
Five-tab bar at 360/390 × EN/CS × dark/light × reduced motion (labels, targets, no hamburger/drawer), the library ⋯ sheet (Import JSON / New folder), the settings sheet (touch targets, key flow, drag-to-close, backdrop), axe contrast audits. |
wizard-test.mjs |
Deck 3-step flow and homework flow, flat action bar, in-page mode switch, the loading lock, abort-on-leave. |
native-test.mjs |
Manifest/PWA head, offline banner + disabled generate, share target GET + POST, Back-gesture layers, undo toast, tab re-tap, haptics, draft restore. |
i18n-test.mjs |
EN/CS dictionary parity, locale switch, Czech desktop shell, Czech phone tab labels and plurals. |
freeze-loading-test.mjs |
The generation loading screen appears immediately, hides the action bar, Cancel returns with the notice. |
review-test.mjs |
Smart Review loading feedback under a stalled request, the session end-to-end, mistakes, and the health-probe cache. |
phase1-test.mjs |
Backup export/import, persistence row, nudge, encrypted sync (enable/join/push/delete + API validation), usage-limit handling (client + a stub Ollama). |
phase2-test.mjs |
Answer history + SRS from a real study run, review/mistakes, stats, exam mode, push reminders hidden without VAPID and validated with it. |
phase3-test.mjs |
Check my work (API + phone/desktop UI), follow-ups, guide step explain, turn-into-a-study-deck. |
chat-test.mjs |
Chat: streaming API (validation, allowlist, context travel, history window, thinking separation, usage-limit mapping), attachment extraction, entry points, streaming/stop, markdown + KaTeX, model/scope pickers, edit/regenerate, offline, reduced motion, plus history (IDB persistence, reload, rename/search/delete/undo, scope+model memory), assistant actions, the export payload and a two-device sync round-trip. |
Extra instances
phase1, phase2 and phase3 start their own next start instance with a
stub Ollama (or VAPID keys) on a spare port (3208/3209). Each suite checks the
port is free first and kills the whole process group on exit, so ports do not
leak between suites. Scratch data for the VAPID test lives in tests/.tmp/
(gitignored).
Diagnostics (not part of the run)
node tests/bubble-perf.mjs [label] measures the ice-scene frame cost with a
CDP performance trace (rAF frame timing, long tasks, main-thread busy time,
style recalcs) on a 4× throttled phone profile and a 2× desktop profile. It
always exits 0; the numbers are for tuning the bubble count/speed.