Files
yellowjacket/e2e/playwright.config.ts
T
logan 5ca6cad45a
Build & publish Arch package / arch-package (push) Successful in 2m8s
CI / check (push) Failing after 1m56s
CI / e2e (push) Skipped
Search index maintenance / maintain-index (push) Successful in 13s
feat(harness): agent-drivable dev harness and CI that gates
A coding agent could develop this repo's Go packages and could not
develop the application: every path to running YellowJacket ended in a
blocking GTK window, so 265 bound methods, 46 events, 33 component
directories and 13 stores had exactly one form of verification
available — `tsc --noEmit`.

The unlock is that `wails dev`'s dev server on :34115 serves the real
frontend with the real generated bindings against the same Go backend a
desktop window attaches to, so a plain Chromium under Xvfb gets a fully
functional app. Four test tiers now exist, cheapest first:

- `make ui-test` — 313 Vitest tests in a real browser in ~2 s, no app,
  no backend, no display. Works because `frontend/wailsjs/` is a pure
  passthrough to `window.go`/`window.runtime`, so faking just those two
  globals runs the real bindings and the real store code.
- `make test` — services in-process, asserting on the payload the
  frontend would receive, via a new `events.Emit` wrapper.
- `make dev-headless` + `playwright-cli` — the real app, driven
  interactively, with an event bridge on `window.__yjEvents` and a
  dev-only control surface at `/__test/`.
- `make e2e` — 19 of those flows frozen as Playwright specs.

`events.Emit(ctx, …)` replaces all 35 direct `runtime.EventsEmit` call
sites: wails' `getEvents` `log.Fatalf`s on any context without its
runtime, so those paths could not run under test and a background
worker could take the app down. Four packages had each hand-rolled the
same guard; nine more guarded on `ctx != nil`, which does not help.
`TestNoDirectRuntimeEmits` fails the build on a new one.

Fixtures are generated, not committed (`make testdata`), and seeds are
built by *running the app* — never by hand-writing config and DB rows,
which would be a second description of a valid YJ_HOME.

`.gitea/workflows/ci.yml` is the first workflow here that tests
anything; the other three only package, so `gitea_ci` reported only
packaging jobs and misled anyone asking whether a push was healthy.
Both jobs were prototyped to green in a bare ubuntu:24.04 container
before the YAML was written, which immediately caught `make lint`
linting three configurations that nothing builds: all three passes
omitted `webkit2_41`, so wails resolved webkit2gtk-4.0 — which Arch
still ships and Ubuntu 24.04 dropped.

Operational instructions live in `.pi/skills/yellowjacket-dev/`,
measured discoveries in `.planning/NOTES.md`, and architecture in
`CLAUDE.md` — split by tense, not by topic, because a topical split
gives every new fact two plausible homes. `make skill-check` fails a
commit if the skill cites a make target that does not exist.
2026-08-10 23:20:42 -04:00

50 lines
1.9 KiB
TypeScript

import { defineConfig, devices } from '@playwright/test';
/**
* These specs drive the *real* application: the Wails dev server on
* :34115 serves the real frontend with real bindings on `window.go`,
* bridged to the same Go backend a desktop window would use. Nothing
* here is mocked.
*
* The app is not started by Playwright. `make dev-headless` daemonises
* (it writes .dev/app.pid and returns), which is the opposite of what
* `webServer` expects to supervise, and starting it per-run would also
* mean rebuilding the frontend per-run. globalSetup checks it is up
* and says exactly what to run if it is not.
*
* WebKit is CI-only: Playwright's Linux WebKit build links Ubuntu 24.04
* libraries that Arch does not provide, so it cannot start on a local
* dev machine. It is the closest available approximation of the
* WebKit2GTK renderer we actually ship, so CI runs it and local runs
* do not.
*/
const PORT = Number(process.env.YJ_E2E_PORT ?? 34115);
export default defineConfig({
testDir: './specs',
globalSetup: './support/global-setup.ts',
// The backend is a single shared process with one SQLite database, so
// parallel workers would fight over the same state.
workers: 1,
fullyParallel: false,
forbidOnly: !!process.env.CI,
retries: process.env.CI ? 1 : 0,
reporter: process.env.CI ? [['github'], ['html', { open: 'never' }]] : [['list']],
timeout: 30_000,
expect: { timeout: 10_000 },
use: {
baseURL: `http://localhost:${PORT}`,
testIdAttribute: 'data-testid',
viewport: { width: 1440, height: 900 },
trace: 'retain-on-failure',
screenshot: 'only-on-failure',
video: process.env.CI ? 'retain-on-failure' : 'off',
},
projects: [
{ name: 'chromium', use: { ...devices['Desktop Chrome'] } },
...(process.env.YJ_E2E_WEBKIT
? [{ name: 'webkit', use: { ...devices['Desktop Safari'] } }]
: []),
],
});