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.
72 lines
2.1 KiB
TypeScript
72 lines
2.1 KiB
TypeScript
/**
|
|
* Helpers on top of the Wails fake: pushing backend events, stubbing
|
|
* bound methods, and inspecting what the frontend called back.
|
|
*/
|
|
import { wails, type BindingCall } from './wails-fake';
|
|
|
|
export { wails } from './wails-fake';
|
|
|
|
/**
|
|
* Push a backend event into the page, exactly as `runtime.EventsEmit`
|
|
* on the Go side would. Extra arguments become the event's data array.
|
|
*/
|
|
export function emit(name: string, ...data: unknown[]): void {
|
|
wails.notify(name, data);
|
|
}
|
|
|
|
/**
|
|
* Register the return value of a bound method. The path is the one the
|
|
* generated bindings use — `service.Type.Method`, e.g.
|
|
* `config.Config.GetShortcuts`.
|
|
*
|
|
* A function value is called with the invocation's arguments, so a stub
|
|
* can vary by input.
|
|
*/
|
|
export function stub(path: string, value: unknown): void {
|
|
wails.stub(path, value);
|
|
}
|
|
|
|
/**
|
|
* Make a bound method fail, as a Go method returning an error does:
|
|
* the promise rejects, it does not throw into the caller.
|
|
*/
|
|
export function stubFailure(path: string, message = 'backend error'): void {
|
|
wails.stub(path, () => {
|
|
throw new Error(message);
|
|
});
|
|
}
|
|
|
|
/** Every call made to a bound method, in order. */
|
|
export function calls(path?: string): BindingCall[] {
|
|
if (path === undefined) return wails.calls.slice();
|
|
|
|
return wails.calls.filter((c) => c.path === path);
|
|
}
|
|
|
|
/** The most recent call to `path`, or undefined. */
|
|
export function lastCall(path: string): BindingCall | undefined {
|
|
return calls(path).at(-1);
|
|
}
|
|
|
|
/** The argument list of the most recent call to `path`. */
|
|
export function lastArgs(path: string): unknown[] | undefined {
|
|
return lastCall(path)?.args;
|
|
}
|
|
|
|
/**
|
|
* Flush pending microtasks. Stores coalesce subscriber notification
|
|
* through `queueMicrotask`, so state is observable immediately but
|
|
* subscribers are not — anything asserting on a subscriber must await
|
|
* this first.
|
|
*/
|
|
export async function flush(): Promise<void> {
|
|
await new Promise<void>((resolve) => {
|
|
setTimeout(resolve, 0);
|
|
});
|
|
}
|
|
|
|
/** Clears recorded calls and stubs between tests. */
|
|
export function resetHarness(): void {
|
|
wails.reset();
|
|
}
|