You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have at least a few tests that make actual http requests and smart contract calls to a publicly available Tableland Network. I'll suggest that this can be the "staging" Tableland Network, but testnet could work too, or we could add the tooling to spin up a network via https://github.com/textileio/local-tableland
The text was updated successfully, but these errors were encountered:
On Jun 9, 2022, 2:33 PM -0700, Joe Wagner ***@***.***>, wrote:
We should have at least a few tests that make actual http requests and smart contract calls to a publicly available Tableland Network. I'll suggest that this can be the "staging" Tableland Network, but testnet could work too, or we could add the tooling to spin up a network via https://github.com/textileio/local-tableland
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
Local might be nicer, otherwise we’d have to manage a wallet for tests, but that might not be too much of a headache
That's a good point, I hadn't thought about managing the wallet keys.
If we spin up a local instance I think we would need the go-validator code base, still a private repo but not for long, and docker available to the test runner. Figuring out the key management might be less of a headache?
We should have at least a few tests that make actual http requests and smart contract calls to a publicly available Tableland Network. I'll suggest that this can be the "staging" Tableland Network, but testnet could work too, or we could add the tooling to spin up a network via https://github.com/textileio/local-tableland
The text was updated successfully, but these errors were encountered: