Fission 0.11.1: Web LiveTest

Drive real Fission Web applications in Chromium with the same semantic test contract used by native shells.
2026-08-17
By Fission Team
Releases
You can now use LiveTest against a real Web app. Fission 0.11.1 lets a test launch Chromium, query the Fission semantic tree, find widgets with semantic selectors, send deterministic input, control time, wait for app state, and capture PNG screenshots. It uses the same LiveTestClient as the native shells, so there is no second testing API to learn.

One testing vocabulary

Web testing uses the same TestCommand, SelectorQuery, TestEvent, and TestResponse types as native testing. Canvas-rendered widgets are found through Fission semantics, not a separate set of DOM selectors:
let client = LiveTestClient::launch_browser(
    BrowserTestOptions::new("http://127.0.0.1:8080/").fission_canvas(),
)?;

client.wait_for_text("Inbox", 5_000)?;
client.tap_semantic_identifier("inbox.compose")?;
client.fill_text_semantic_identifier("message.subject", "Hello from Web")?;
client.wait_for_idle(5_000, true)?;
let screenshot = client.capture_screenshot_png()?;
Native callers still use LiveTestClient::connect(port). The browser API is additive; it does not change the native transport.
The application must already be served from a matching Web test build. FISSION_WEB_TEST_CONTROL=1 is a compile-time WASM input; setting it only on the test process after the app was built does not install the bridge. The current testing reference also distinguishes retained canvas mode from generic website mode introduced later.

The CLI proves live control

fission test --target web does more than check that a canvas appeared. It builds WASM with test control enabled, serves it on a temporary loopback port, starts an isolated headless Chromium profile, pumps the Web event loop, and queries the running semantic tree. A build, browser, bridge, or protocol error fails the command.
Ordinary Web builds do not install the test bridge. The bridge opens no application control port and is selected only when producing a Web test build.

Intentionally bounded

The first version supports Chromium without adding Playwright, Selenium, or WebDriver. Input goes through Fission's deterministic event path; these are not trusted, browser-generated events. Screenshots capture the browser page, including the canvas and browser-composited surfaces, rather than reading back a WebGPU texture. Tests inspect Fission's semantic tree. Browser accessibility tree assertions and Firefox or WebKit drivers are still future work.
Those limits keep the implementation focused while giving native and Web tests the same contract. The transport leaves room for another browser driver later without changing the application tests.

Upgrade

Update the application dependency:
fission = { version = "0.11.1", default-features = false, features = ["web"] }
Install the matching CLI for fission test --target web:
cargo install cargo-fission --version 0.11.1 --locked
The complete design and deferred scope are recorded in docs/rfc-web-testing.md.