wasmfixture

Overview ¶

Package wasmfixture guards the tests that load the echo app fixture (internal/wasmplugin/testdata/echo/echo.wasm): the module is built, and it was built from the sources beside it.

⚠⚠ echo.wasm is a build artefact nobody commits. A tree that merged a change to the fixture's main.go or manifest.json keeps the module it built before: on 2026-09-25 four tests of #64 failed on main with a bare 502 ("gather" is not an action of the module that was loaded) while the branch they came from was green. CI builds the module first and is not affected; a developer tree is. A stale module is a failure with the command to run, never a skip.

Stdlib only: internal/testutil imports the API, which imports wasmplugin, so wasmplugin's own tests cannot use it.

⚠⚠ The same rule lives in TypeScript for the e2e specs that install the module (e2e/helpers/echoFixture.ts): on the v0.50.0 pretag spec 192 ran a stale echo.wasm, because the e2e side only asked whether the file existed. Change the two together; web/tests/deploy/echoFixture.test.ts reads the file set below and holds the TypeScript one to it.