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.7 KiB
TypeScript
69 lines
2.7 KiB
TypeScript
import { test, expect } from '../support/fixtures.js';
|
|
|
|
/**
|
|
* The library views, against the generated fixture library
|
|
* (`make testdata`): 31 tracks chosen to cover the cases the app has
|
|
* code for — unicode and RTL titles, missing tags, a deliberately
|
|
* absurd artist name for truncation, duplicates.
|
|
*/
|
|
test.describe('library views', () => {
|
|
test('lands in the app, not the first-run wizard', async ({ app }) => {
|
|
// A fresh YJ_HOME puts <first-run-wizard> over everything and it
|
|
// intercepts every pointer event, so "the click did nothing" is the
|
|
// symptom of an unseeded sandbox rather than a broken control.
|
|
//
|
|
// Asserted by clicking rather than by inspecting the wizard element:
|
|
// the element is always in the DOM and merely renders nothing once a
|
|
// library exists, so its presence proves nothing. Playwright's own
|
|
// actionability check fails a covered click with "intercepts pointer
|
|
// events", which is exactly the condition worth catching.
|
|
await expect(app.getByTestId('track-row').first()).toBeVisible();
|
|
await app.getByTestId('nav-artists').click({ timeout: 5_000 });
|
|
|
|
await expect(app.getByTestId('main-content')).toHaveAttribute(
|
|
'data-active-view',
|
|
'artists',
|
|
);
|
|
});
|
|
|
|
test('renders every fixture track, unicode included', async ({
|
|
app,
|
|
testctl,
|
|
}) => {
|
|
const health = await testctl.health();
|
|
const rows = app.getByTestId('track-row');
|
|
|
|
await expect(rows).toHaveCount(health.counts.tracks);
|
|
|
|
// Non-Latin scripts survive the tag reader, the database and the
|
|
// renderer. These titles exist in the fixtures for this reason.
|
|
await expect(app.getByText('Привет мир')).toBeVisible();
|
|
await expect(app.getByText('さくら')).toBeVisible();
|
|
await expect(app.getByText('مرحبا بالعالم')).toBeVisible();
|
|
});
|
|
|
|
test('the sidebar navigates between primary views', async ({ app }) => {
|
|
const main = app.getByTestId('main-content');
|
|
|
|
for (const view of ['artists', 'genres', 'albums', 'playlists', 'tracks']) {
|
|
await app.getByTestId(`nav-${view}`).click();
|
|
await expect(main).toHaveAttribute('data-active-view', view);
|
|
await expect(app.getByTestId(`nav-${view}`)).toHaveAttribute(
|
|
'aria-current',
|
|
'page',
|
|
);
|
|
}
|
|
});
|
|
|
|
test('the artists view shows the fixture artists', async ({ app }) => {
|
|
await app.getByTestId('nav-artists').click();
|
|
await expect(app.getByTestId('main-content')).toHaveAttribute(
|
|
'data-active-view',
|
|
'artists',
|
|
);
|
|
|
|
await expect(app.getByText('Aurora Fields').first()).toBeVisible();
|
|
await expect(app.getByText('Pale Circuit').first()).toBeVisible();
|
|
});
|
|
});
|