Context
Issue #1 introduced wit-bindgen composed-runner components as test cases. We now have 4 fixtures passing with full runtime verification (numbers, strings, lists, records).
Remaining type families
The wit-bindgen test suite covers additional type families that would exercise more adapter code paths:
How to generate
From the wit-bindgen source tree:
wit-bindgen test --languages rust --artifacts artifacts \
--rust-wit-bindgen-path crates/guest-rust/ tests/runtime
Fixtures end up in artifacts/<name>/composed-runner.rs-test.rs.wasm.
Test structure
Follow the existing pattern in meld-core/tests/wit_bindgen_runtime.rs:
- Fusion as CoreModule — validate with wasmparser
- Fusion as Component — validate
- Runtime execution — fuse, load in wasmtime with WASI, call
run()
ref #1
Context
Issue #1 introduced wit-bindgen composed-runner components as test cases. We now have 4 fixtures passing with full runtime verification (numbers, strings, lists, records).
Remaining type families
The wit-bindgen test suite covers additional type families that would exercise more adapter code paths:
variant,enum,option<T>,result<T, E>How to generate
From the wit-bindgen source tree:
wit-bindgen test --languages rust --artifacts artifacts \ --rust-wit-bindgen-path crates/guest-rust/ tests/runtimeFixtures end up in
artifacts/<name>/composed-runner.rs-test.rs.wasm.Test structure
Follow the existing pattern in
meld-core/tests/wit_bindgen_runtime.rs:run()ref #1