Need smoke-screen tests to ensure that the SDK works with an actual Tableland Network

[joewagner]

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

[sanderpick]

Local might be nicer, otherwise we’d have to manage a wallet for tests, but that might not be too much of a headache

…

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: ***@***.***>

[joewagner]

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?

[joewagner]

All that said, long term being able to use a local network seems good and doable once go-tableland is public