Per discussion in bug 1855254, it will be nice to add tests for rendered text for wasm in the debugger panel, for particular features. For example, to verify if Wasm GC is supported, and debugger is not failing. From https://phabricator.services.mozilla.com/D189546: > In the past we just agreed to do a simple smoke test that uses some internal function (renderWasmText). For example, I see https://searchfox.org/mozilla-central/source/devtools/client/debugger/src/utils/tests/wasm.spec.js#56 but not sure if it is still in use. > The testing for particular features are normally covered by testing on the https://github.com/wasdk/wasmparser/ CI. Though I see no harm on adding some on our side. I'll create a bug for it
Bug 1855778 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Per discussion in bug 1855254, it will be nice to add tests for rendered text for wasm in the debugger panel, for particular features. For example, to verify if Wasm GC is supported, and debugger is not failing. From https://phabricator.services.mozilla.com/D189546: > In the past we just agreed to do a simple smoke test that uses some internal function (renderWasmText). For example, I see https://searchfox.org/mozilla-central/source/devtools/client/debugger/src/utils/tests/wasm.spec.js#56 but not sure if it is still in use. > The testing for particular features are normally covered by testing on the https://github.com/wasdk/wasmparser/ CI. Though I see no harm on adding some on our side.