lightninglabs / lightninglabs/lightning-node-connect
itests: expand end to end test suite to include node.js process with a wasm connection
@guggero is already working on this.
Since Nov 16, 2021.
- Dominant language
- Go
- Stars
- 85
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
We should extend our test suite to also cover the browser portion. We leanred earlier this week that Go will actually change the `wasm_exec.js` from time to time. To increase confidence in the changes we make, we should also extend the test suite to exercise the _browser_ portion of the system.
# Steps To Completion
- [ ] Within the integration tests, spin a simple `node.js` process (or some headless browser system) that's loaded with the sample WASM client.
- [ ] In addition to the Go client, use the above client within the integration tests (by Go version) to exercise full end to end behavior.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.