Open Bug 1855778 Opened 8 months ago Updated 2 months ago

Add tests to verify if particular wasm proposal is supported in the debugger

Categories

(DevTools :: Debugger, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: yury, Unassigned)

References

(Blocks 2 open bugs)

Details

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.

Type: enhancement → task
Priority: -- → P3

(In reply to Yury Delendik (:yury) from comment #0)

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.

This test is still in use and we will take care of maintaining it. We would like to eventually convert these node jest tests to xpcshell/mochitests to ease running them.

For now, you have to do:

$ cd devtools/client/debugger
$ yarn
$ yarn test src/utils/tests/wasm.spec.js
Depends on: 1885589
You need to log in before you can comment on or make changes to this bug.