We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, we spin up a number of rpc servers, and use the client-runner ts-node script to drive them.
client-runner
A better solution would be to write a jest test to replace the ts-node script.
It should follow https://github.com/statechannels/go-nitro/blob/e8451e1a633a490056dbb9d2b047a32f263ec75a/node_test/rpc_test.go in terms of what it looks to cover.
It should be kept separate from unit tests (i.e. a separate script in the package manifest, possibly a separate jest config)
It may want to pull in some of the isServerUp helpers from the client runner.
isServerUp
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, we spin up a number of rpc servers, and use the
client-runner
ts-node script to drive them.A better solution would be to write a jest test to replace the ts-node script.
It should follow https://github.com/statechannels/go-nitro/blob/e8451e1a633a490056dbb9d2b047a32f263ec75a/node_test/rpc_test.go in terms of what it looks to cover.
It should be kept separate from unit tests (i.e. a separate script in the package manifest, possibly a separate jest config)
It may want to pull in some of the
isServerUp
helpers from the client runner.The text was updated successfully, but these errors were encountered: