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.
69 lines
2.2 KiB
TypeScript
69 lines
2.2 KiB
TypeScript
import { test, expect, resetEvents, waitForEvent } from '../support/fixtures.js';
|
|
|
|
/**
|
|
* The dev-only control surface (backend/testctl), which exists for the
|
|
* things a browser genuinely cannot do.
|
|
*/
|
|
test.describe('control surface', () => {
|
|
test('database snapshot and restore round-trip', async ({ testctl }) => {
|
|
// VACUUM INTO copies the whole file and the restore copies every
|
|
// row back; on a database carrying an explore catalog that is tens
|
|
// of seconds, not the default 30s budget for a whole test.
|
|
test.setTimeout(180_000);
|
|
|
|
const before = (await testctl.health()).counts.tracks;
|
|
|
|
await testctl.snapshot('e2e-pristine');
|
|
await testctl.sql('DELETE FROM audio_files');
|
|
|
|
expect((await testctl.health()).counts.tracks).toBe(0);
|
|
|
|
// Restore copies rows rather than files, because the app holds the
|
|
// database open across two connection pools and cannot be made to
|
|
// reopen it from here.
|
|
await testctl.restore('e2e-pristine');
|
|
|
|
expect((await testctl.health()).counts.tracks).toBe(before);
|
|
});
|
|
|
|
test('a forced backend event reaches the browser', async ({
|
|
app,
|
|
testctl,
|
|
}) => {
|
|
// LibraryScanProgress normally only arrives during a real scan.
|
|
// Emitting it directly is how a push-driven view gets exercised
|
|
// without staging the work that would produce it.
|
|
await resetEvents(app);
|
|
await testctl.emit('LibraryScanProgress', {
|
|
current: 7,
|
|
total: 31,
|
|
currentFile: 'probe.mp3',
|
|
});
|
|
|
|
const ev = await waitForEvent(app, 'LibraryScanProgress');
|
|
|
|
expect(ev.data[0]).toMatchObject({ current: 7, total: 31 });
|
|
});
|
|
|
|
test('sql reads return rows, writes return a count', async ({ testctl }) => {
|
|
const read = await testctl.sql(
|
|
'SELECT COUNT(*) AS n FROM audio_files',
|
|
);
|
|
|
|
expect(read.rows[0].n).toBeGreaterThan(0);
|
|
|
|
const write = await testctl.sql(
|
|
'UPDATE player_state SET volume = volume',
|
|
);
|
|
|
|
expect(write).toHaveProperty('rowsAffected');
|
|
});
|
|
|
|
test('bad input is rejected with a reason, not a bare status', async ({
|
|
testctl,
|
|
}) => {
|
|
await expect(testctl.snapshot('../escape')).rejects.toThrow(/name must/);
|
|
await expect(testctl.restore('nope')).rejects.toThrow(/no such snapshot/);
|
|
});
|
|
});
|