I don't know how other wasm WPT tests are written, but it'd be helpful to also have the .wat file to:

• see what the .wasm file is actually doing
• to be able to edit the test if needed

Mostly we've dynamically generated wasm binaries from js within the test, but I agree we shouldn't put binary wasm in the repo without a source and perhaps added to tools/ci/update_built.py

@Ms2ger yes we can't dynamically construct Wasm when testing static imports. Note that we already have multiple compiled Wasm cases in the webapi folder:

• https://github.com/web-platform-tests/wpt/tree/master/wasm/webapi/esm-integration/resources has various wasm binaries
• https://github.com/web-platform-tests/wpt/tree/master/wasm/webapi/resources has a couple as well

In general the main loss over having something like .wat is just being able to have comments.

The ideal approach might be to have a WPT harness approach that allows file.wat to be served as file.wasm so we can then support commented WAT.

I wonder if something like that might be possible? I think it should be a separate PR though.

The ideal approach might be to have a WPT harness approach that allows file.wat to be served as file.wasm so we can then support commented WAT.

That would be really nice, if possible. In general the text format is so much easier to use.

GH has support for displaying binary files specially depending on their file format. I opened a community discussion to see if they would consider adding wasm support.

The feedback here has now been addressed.