These are the largest test suites, and most common to run in day to day
wasm-bindgen development. These tests are compiled to Wasm and then run in
Node.js or a headless browser via the WebDriver protocol.
cargo test --target wasm32-unknown-unknown
for details and configuring which headless browser is used.
This small test suite just verifies that exported
wasm-bindgen methods can
still be used on the native host's target.
cargo test -p webidl-tests --target wasm32-unknown-unknown
These tests assert that we have reasonable error messages that point to the
right source spans when the
#[wasm_bindgen] proc-macro is misused.
cargo test -p ui-tests