Currently, we have some messy, not versioned, Go tests, that some of us run manually on the local development environment, to check whether the WASM module works correctly or not. However, that has many evident drawbacks (no actually automated tests, tests don't go with source code, etc), and is kind of a blocker or prerequisite for #19 and #49 .
So, as the main reason behind that is that running Go tests for GOOS=js GOARCH=wasm is a bit tricky, I propose to add wasmbrowsertest to the project (I tested it locally and it works fine!), so we can:
Start versioning our Go tests
Let anyone run on their own with a simple make command.
Currently, we have some messy, not versioned, Go tests, that some of us run manually on the local development environment, to check whether the WASM module works correctly or not. However, that has many evident drawbacks (no actually automated tests, tests don't go with source code, etc), and is kind of a blocker or prerequisite for #19 and #49 .
So, as the main reason behind that is that running Go tests for
GOOS=js GOARCH=wasmis a bit tricky, I propose to add wasmbrowsertest to the project (I tested it locally and it works fine!), so we can:makecommand.