logan
5ca6cad45a
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.
70 lines
2.8 KiB
TypeScript
70 lines
2.8 KiB
TypeScript
/**
|
|
* Runs before every test module. Two jobs, in this order:
|
|
*
|
|
* 1. Install the Wails fake. Store singletons call `EventsOn` and load
|
|
* from the backend *in their constructors*, which run when a test
|
|
* module imports them — so the globals have to exist first.
|
|
* 2. Point Web Awesome at its assets. Without this every `<wa-icon>`
|
|
* silently 404s and screenshots come out with holes in them.
|
|
*/
|
|
import { afterEach, beforeEach } from 'vitest';
|
|
import { setBasePath } from '@awesome.me/webawesome/dist/webawesome.js';
|
|
import '@awesome.me/webawesome/dist/styles/themes/default.css';
|
|
import { installWailsFake, wails } from './support/wails-fake';
|
|
import { resetHarness } from './support/harness';
|
|
import { cleanupFixtures } from './support/render';
|
|
|
|
installWailsFake();
|
|
|
|
/**
|
|
* A few stores read config in their constructor, which runs when a test
|
|
* module imports them — before any test has had a chance to stub. An
|
|
* unstubbed binding resolves undefined, and `themeStore` in particular
|
|
* then derives a colour ramp from `undefined` and throws inside its own
|
|
* failure handler. These defaults keep import-time loads on the happy
|
|
* path; tests still stub whatever they assert on.
|
|
*/
|
|
const importTimeDefaults: Array<[string, unknown]> = [
|
|
['config.Config.GetThemeAccentColor', '#ffd43b'],
|
|
['config.Config.GetThemeBackgroundShade', 'dark'],
|
|
['config.Config.GetShortcuts', {}],
|
|
// libraryStore and playlistStore fetch eagerly at import. Left
|
|
// unstubbed they would cache `undefined` — not the empty list Go
|
|
// sends — and every consumer would then crash on `.length`.
|
|
['library.Library.GetAllTracks', []],
|
|
['library.Library.GetAllAlbums', []],
|
|
['library.Library.GetAllArtists', []],
|
|
['library.Library.GetAllGenresWithCounts', []],
|
|
['library.Library.GetAllLibrariesWithTrackCounts', []],
|
|
['playlist.Service.GetAllPlaylistsWithTracks', []],
|
|
];
|
|
|
|
for (const [path, value] of importTimeDefaults) {
|
|
wails.stub(path, value);
|
|
}
|
|
|
|
// Vite serves the dependency's own directory, so icons resolve from
|
|
// node_modules rather than from the built `dist/webawesome` copy the
|
|
// app uses.
|
|
setBasePath('/node_modules/@awesome.me/webawesome/dist');
|
|
|
|
// index.ts imports the theme store for its side effect: it derives the
|
|
// --yj-* custom properties and applies them to :root, where every
|
|
// shadow root inherits them. Without it a component renders white text
|
|
// on a white page and screenshots come out blank.
|
|
await import('@store/theme-store');
|
|
|
|
// The app's surface colours come from index.css, whose grid layout is
|
|
// not wanted here — take the two declarations that matter.
|
|
document.body.style.backgroundColor = 'var(--yj-bg-base, black)';
|
|
document.body.style.color = 'var(--yj-text-primary, white)';
|
|
document.body.style.margin = '0';
|
|
|
|
beforeEach(() => {
|
|
resetHarness();
|
|
});
|
|
|
|
afterEach(() => {
|
|
cleanupFixtures();
|
|
});
|