Testing integrations

Test each layer separately

A runtime transcript shows what core prepared. A DOM test shows how the page changed. Test with a real screen reader to confirm what it speaks.

Test every supported browser engine

Browser fixtures run in Chromium, Firefox, and WebKit. They check keyboard use, stable focus, page landmarks, live regions, and page announcements.

pnpm test:browser:install
pnpm test:browser

Test a realistic app workflow

Fixtures cover streaming text, tool updates, stopping, retrying, and browser announcements. Each assertion names the behavior it checks.

• Run the same scenarios in all three browser engines.
• Check that streaming and status updates do not move focus.
• Connect each app event to the runtime update and the resulting page change.
• Keep controls and visible status usable without the library.

Record hands-on screen-reader tests

For each release, record the date, browser, operating system, screen reader and version, workflow, expected result, actual result, and outcome. Repository validation checks every required field.

Use ManualClock for time-dependent behavior

Advance the test clock instead of waiting for real timers. Check diagnostics when the runtime intentionally skips an update.

const recorder = createAnnouncementRecorder({ preset: "balanced" });
const runtime = recorder.runtime;
const clock = recorder.clock;

runtime.dispatch(started);
runtime.dispatch(delta);
clock.advanceBy(2_000);

expect(recorder.transcript()).toHaveLength(1);