Open justinmoon opened 3 years ago
I think this is because the tests depend on our testutils
crate, which itself depends on electrum-client
to interact with the electrum server while the end to end tests are running. Things like waiting for the electrum server to index a transaction before moving forward, or waiting for the chaintip to update.
I guess we could use conditional compilation to exclude some parts when running under wasm32, but I haven't bothered doing that yet because it's not that easy to run the tests on a non-native platform: I think the output of cargo test
would be a wasm32 binary somewhere in ./target/wasm32-unknown-unknown
, and then you would have to write a js wrapper to load that in a browser to actually run the test, you can't just run that from your command line unfortunately.
Observed this testing out #174. Seems like the
socks
crate isn't compatible with WASM?? Our CI doesn't seems to experience this because it just runscargo check
and notcargo test
.