Nightly deployment testing

[jennijuju]

As we are making changes across the stack in multiple repos, I think it would be useful for us to spin up a nightly deployment E2E testing flow that pulls the latest commit from main for Synapse, Filecoin Pay, FilecoinWarmStorageService, Filecoin PDP, and Curio, and runs some testing, starting with a happy path to capture unintentional breaking changes/bugs. The test runs in the Filecoin Calibnet testnet. Roughly, the flow will look like:

• Create a burner master wallet and use it for contract deployment
• Get test FIL to the burner wallet
• Deploy Filecoin Pay contract
• Deploy Filecoin PDP contract
• Deploy Filecoin Warm Storage contract
• Spin up a Curio PDP node that listens to the Filecoin PDP/Warm Storage Service contract
• Add Curio PDP miner to the Filecoin Warm Storage contract and use the master account to approve it
• Get test FIL to Curio miner wallet
• Start Synapse SDK with a client wallet
• Get test FIL, swap for USDFC; authorize and make a deposit to Filecoin Warm Storage service
• Create a proof set without addCDN
• synapse.upload a couple of roots
• synapse.download a root
• Create a proof set with addCDN
• synapse.upload a couple of roots
• synapse.download a root from FilCDN URL
• synapse.settle as a SP after a couple of epochs
• synapse.settke as FilCDN after a couple of epochs
• Make sure a PDP proof passes

Goals:

• Catch breaking changes or regressions across the involved repositories.
• Expand test coverage over time, starting with the happy path.
• Ensure e2e integration on the Filecoin Calibnet testnet.

[jennijuju]

@rvagg mentioned he had some part of the test flow somewhere can be used

[rjan90]

I think these parts:

• Create a burner master wallet and use it for contract deployment
• Get test FIL to the burner wallet
• Deploy Filecoin Pay contract
• Deploy Filecoin PDP contract
• Deploy Filecoin Warm Storage contract

Are covered by: #106 and the PR which has been opened here: #116

[hugomrdias]

https://github.com/hugomrdias/metamask for browser/metamask automation

[rvagg]

Yes, I have a script that does a lot of the set up for me, it's a bit targeted to a specific type of testing I've been doing but could be easily repurposed but essentially it's a combination of the process embedded in these:

• https://github.com/FilOzone/pdp/blob/main/tools/deploy-calibnet.sh
• https://github.com/FilOzone/filecoin-services/blob/main/service_contracts/tools/deploy-warm-storage-calibnet.sh
• https://github.com/FilOzone/synapse-sdk/blob/master/utils/post-deploy-setup.js

I haven't needed Payments deployment so that's not included but this exists which should be able to do all three: https://github.com/FilOzone/filecoin-services/blob/main/service_contracts/tools/deploy-all-warm-storage-calibnet.sh

https://github.com/FilOzone/synapse-sdk/blob/master/utils/example-storage-e2e.js is my go-to e2e test script assuming all the pieces are running, it keeps evolving as features are added or changed (and is about the only thing in utils/ that I make sure is updated and working because I'm always using it).

Doing the Curio setup is another matter that I've only done through the guided-setup process; that's all nicely documented in filecoin-project/curio#554 but it's nowhere near an automated setup process. I imagine setting a new Curio node will involve having a database dump that can be restored, or some SQL that can be run against a newly installed Curio.

[rvagg]

I have a script that does a lot of the set up for me

Lost it .. I think I accidentally deleted it, at least I can't find it anymore! So the above will have to do!