Javascript Web Bindings Need Tests

[xstoicunicornx]

This issue is to track follow up from #1513.

Javascript web bindings have now been implemented but still need targeted testing. Currently only the nodejs bindings have test coverage.

[caarloshenriq]

I’d like to work on this one. I have background with JavaScript/web development, so I can help add targeted test coverage for the web bindings

[xstoicunicornx]

That would be wonderful!

I did do some preliminary research into how to test the web portion (since I'm not actually familiar with what the recommendation should be) and the two main methods I was looking into were:

• Jest which seems to have experimental support for ESMAScript modules (https://jestjs.io/docs/ecmascript-modules)
• Wasm-bindgen-test though I hadn't yet dug into how rust code can test js modules (https://wasm-bindgen.github.io/wasm-bindgen/wasm-bindgen-test/browsers.html#running-the-tests-in-the-headless-browser)

IMO the main objective is to test the ESMAScript module provided by the web bindings, as the CommonJS module provided by the nodejs bindings is covered by existing tests. However, it would be nice if both used the same testing infrastructure (and it is probably pretty low effort to rewrite the existing tests using a new framework with AI help).

The only reason I was considering the wasm-bindgen-test option is that the JS bindings are already being produced by the wasm-bindgen library (uniffi-bindgen-react-native creates the rust code for wasm-bindgen to transform into wasm with js bindings) so could potentially be a good fit. But again I hadn't yet understood how rust code would test the js modules.

If you have a different opinion/alternate suggestions on anything I said above I am all ears. Especially if there is a way to test the ESMAScript modules without any new dependencies.