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.
124 lines
3.7 KiB
TypeScript
124 lines
3.7 KiB
TypeScript
/**
|
|
* Mounting helpers for component tests.
|
|
*
|
|
* Components are mounted into a real document and queried through their
|
|
* real (open) shadow roots — nothing here approximates the DOM, which
|
|
* is the whole reason this tier runs in a browser.
|
|
*/
|
|
import type { LitElement } from 'lit';
|
|
import { expect } from 'vitest';
|
|
|
|
const mounted: HTMLElement[] = [];
|
|
|
|
/**
|
|
* Create an element, apply properties, mount it and wait for Lit's
|
|
* first render. Properties are set as *properties*, not attributes, so
|
|
* non-string values survive.
|
|
*/
|
|
export async function fixture<T extends LitElement>(
|
|
tag: string,
|
|
props: Record<string, unknown> = {},
|
|
): Promise<T> {
|
|
const el = document.createElement(tag) as T;
|
|
|
|
Object.assign(el, props);
|
|
document.body.append(el);
|
|
mounted.push(el);
|
|
|
|
await el.updateComplete;
|
|
|
|
return el;
|
|
}
|
|
|
|
/** Apply properties to a mounted element and wait for the re-render. */
|
|
export async function update<T extends LitElement>(
|
|
el: T,
|
|
props: Record<string, unknown>,
|
|
): Promise<T> {
|
|
Object.assign(el, props);
|
|
el.requestUpdate();
|
|
await el.updateComplete;
|
|
|
|
return el;
|
|
}
|
|
|
|
/** Remove everything mounted by this module. Called from setup. */
|
|
export function cleanupFixtures(): void {
|
|
while (mounted.length > 0) mounted.pop()?.remove();
|
|
}
|
|
|
|
// ===================================================================
|
|
// SHADOW DOM QUERIES
|
|
// ===================================================================
|
|
|
|
/** Query one element inside a component's shadow root. */
|
|
export function shadow<E extends Element = Element>(
|
|
host: Element,
|
|
selector: string,
|
|
): E | null {
|
|
return host.shadowRoot?.querySelector<E>(selector) ?? null;
|
|
}
|
|
|
|
/** Query all matching elements inside a component's shadow root. */
|
|
export function shadowAll<E extends Element = Element>(
|
|
host: Element,
|
|
selector: string,
|
|
): E[] {
|
|
return [...(host.shadowRoot?.querySelectorAll<E>(selector) ?? [])];
|
|
}
|
|
|
|
/** Trimmed text content of the first match, or null if absent. */
|
|
export function text(host: Element, selector: string): string | null {
|
|
return shadow(host, selector)?.textContent?.trim() ?? null;
|
|
}
|
|
|
|
/** Trimmed text content of every match. */
|
|
export function texts(host: Element, selector: string): string[] {
|
|
return shadowAll(host, selector).map((el) => el.textContent?.trim() ?? '');
|
|
}
|
|
|
|
/** The accessible names of every match, for assertions that mirror
|
|
* what a screen reader — and a Playwright selector — would see. */
|
|
export function labels(host: Element, selector: string): string[] {
|
|
return shadowAll(host, selector).map(
|
|
(el) => el.getAttribute('aria-label') ?? '',
|
|
);
|
|
}
|
|
|
|
/** Click something inside a shadow root and let the update settle. */
|
|
export async function click(
|
|
host: LitElement,
|
|
selector: string,
|
|
): Promise<void> {
|
|
const target = shadow<HTMLElement>(host, selector);
|
|
|
|
if (!target) throw new Error(`no element matching ${selector}`);
|
|
|
|
target.click();
|
|
await host.updateComplete;
|
|
}
|
|
|
|
// ===================================================================
|
|
// VISUAL REGRESSION
|
|
// ===================================================================
|
|
|
|
/**
|
|
* Visual regression is opt-in: `toMatchScreenshot` baselines depend on
|
|
* font hinting and compositing, so a baseline taken on one machine
|
|
* fails on another for reasons that have nothing to do with the
|
|
* component. `make ui-visual` sets YJ_VISUAL=1; the default run
|
|
* asserts behaviour only.
|
|
*/
|
|
export const visualEnabled = import.meta.env['YJ_VISUAL'] === '1';
|
|
|
|
/**
|
|
* Screenshot a component against its baseline, when visual regression
|
|
* is enabled. A no-op otherwise — deliberately not a skipped test, so
|
|
* the behavioural assertions around it still run.
|
|
*/
|
|
export async function visual(el: Element, name: string): Promise<void> {
|
|
if (!visualEnabled) return;
|
|
|
|
await expect(el).toMatchScreenshot(name);
|
|
}
|