wasm(fix): failing unit test

[TalDerei]

Fixes breaking changes from #3527 and #3579

[conorsch]

How does one confirm or disprove that this change fixes the test? If I ran cargo test within crates/wasm/, I see all tests passing on both this branch and on main.

[TalDerei]

How does one confirm or disprove that this change fixes the test? If I ran cargo test within crates/wasm/, I see all tests passing on both this branch and on main.

The wasm crate incorporates a unit testing suite that leverages wasm-bindgen-test to simulate a sample spend transaction. For testing purposes, the suite mocks indexDB database calls in an interactive browser accessible at http://127.0.0.1:8000. This requires executing wasm-pack test --chrome -- --test test_build --target wasm32-unknown-unknown --release --features "mock-database" rather than cargo test to check that particular test, and the transaction outputs are accessible in the browser's developer console. The serial and parallel transaction building were failing prior to these changes.

#3503 will eventually integrate this test, and I suspect a more expressive wasm unit testing suite, into the CI using the headless browser mode. That task is currently superseded by higher priority web work.

[conorsch]

Nice, thanks for explaining, @TalDerei! I can now confirm that with the invocation you provided, tests fail on main, as expected, and pass on this branch.