The current architecture is built with limiting wasm32 specific code being minimal so unit tests can run under any target.
However, there're still cases where the repository is broken under wasm32 target but test passes.
This issue aims to add some end-to-end tests that runs in the browser.
The current plan is:
Unit tests and Integration style tests (in dir tests/) are preferred whenever possible as they run under any target, are much faster and wouldn't intermittently fail.
Continue to limit wasm specific code minimal.
Examples also serves as end-to-end test cases (tested with wasm-pack test).
The current architecture is built with limiting
wasm32specific code being minimal so unit tests can run under any target.However, there're still cases where the repository is broken under
wasm32target but test passes.This issue aims to add some end-to-end tests that runs in the browser.
The current plan is:
tests/) are preferred whenever possible as they run under any target, are much faster and wouldn't intermittently fail.wasm-pack test).