The TCK is a test suite for checking conformance of http-wasm implementations versus the http-wasm ABI specification.
This repository contains a standalone runner executable for the http-wasm TCK implemented in Go for use with non-Go host implementations.
The basic steps for running the TCK are
- Implement the backend handler, which is the business logic wrapped by middleware
- Set up the middleware using the TCK guest wasm module
- Start an HTTP server serving this middleware
- Run the tests, pointing at the URL for the HTTP server
Precompiled executables can be downloaded from the releases. A Docker image is also provided as ghcr.io/http-wasm/http-wasm-tck.
The Go implementation of the backend handler can be referred to here.
An HTTP server using this implementation can be started using
http-wasm-tck backend. The server defaults to listening on
0.0.0.0:9080, which can be changed with the -addr flag.
If the port passed to address is 0, for example with
http-wasm-tck backend -addr 0.0.0.0:0, a random port will be chosen. The
backend always prints a message like Started backend server on 0.0.0.0:9080
which can be parsed to find the port if random.
Alternatively, it may be simpler to reimplement the Go implementation of the backend handler into the language of the host.
The guest wasm module can be extracted from the command using
http-wasm-tck extract-guest <path to wasm file>.
With the HTTP server started and serving the middleware and backend, the tests
can be run using http-wasm-tck run. This defaults to issuing requests to
http://localhost:8080, which can be changed with the -url flag.
The entrypoint to this application is in runner_test.go, not a main
package as is typical. See the rationale for more information on why.