Files
yellowjacket/frontend/vitest.config.mts
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

65 lines
2.3 KiB
TypeScript

import path from 'path';
import { playwright } from '@vitest/browser-playwright';
import { defineConfig, mergeConfig } from 'vitest/config';
import viteConfig from './vite.config.mts';
// Visual regression is opt-in. `toMatchScreenshot` baselines are
// sensitive to font hinting and GPU compositing, so a baseline taken on
// one machine fails on another for reasons that have nothing to do with
// the component. Behavioural assertions run everywhere; screenshots run
// where the baselines were taken (`make ui-visual`, or CI's container).
const screenshotsEnabled = process.env['YJ_VISUAL'] === '1';
export default mergeConfig(
viteConfig,
defineConfig({
test: {
// The Playwright *runner* lives in e2e/, a separate package, so its
// specs can never be picked up here and the two Playwright
// versions cannot collide.
include: ['test/**/*.test.ts'],
setupFiles: ['./test/setup.ts'],
globals: false,
browser: {
enabled: true,
provider: playwright(),
headless: true,
// WebKit's Linux build wants Ubuntu libraries Arch does not
// have, so it is a CI-only browser. See .planning/NOTES.md.
instances: [{ browser: 'chromium' }],
viewport: { width: 1280, height: 800 },
screenshotFailures: false,
expect: {
toMatchScreenshot: {
comparatorName: 'pixelmatch',
comparatorOptions: { allowedMismatchedPixelRatio: 0.02 },
},
},
},
expect: { requireAssertions: true },
env: { YJ_VISUAL: screenshotsEnabled ? '1' : '' },
},
resolve: {
alias: {
'@test': path.resolve(__dirname, 'test'),
},
},
// Pre-bundle what the components pull in, or Vite discovers it
// mid-run and reloads the page underneath a running test.
optimizeDeps: {
include: [
'lit',
'lit/decorators.js',
'lit/directives/repeat.js',
'@lit-labs/virtualizer',
// Web Awesome components are deep imports, one per element;
// the glob pre-bundles them all rather than discovering each
// one the first time a component under test imports it.
'@awesome.me/webawesome/dist/components/*/*.js',
'@awesome.me/webawesome/dist/webawesome.js',
],
},
}),
);