To run E2E tests for chainbridge-celo nodes with pre-deployed bridge contracts and elections should be run in same environment.
Currently we use image "chainsafe/chainbridge-bootstrapped-celo" as bootstrapped nodes. This image was build be hands and includes celo nodes with deployed there chainbridge smart contracts. Deployment done with https://github.com/ChainSafe/chainbridge-celo/blob/main/e2e/deploy.go.
We should provide some workflow that build this image automatically when smart contracts being updated.
Implementation details
I think we should build contracts with celo-abigen on any update (version, push to master?) and store them on dockerhub as image (or AWS S3)
Run chainsafe/chainbridge-celo-blockchain image 3 times as 3 nodes of same chain
Installing chainbridge-celo as CLI tool and make deploy with generated (from step 1)
Make dumps of each running node with deployed scripts
To run E2E tests for chainbridge-celo nodes with pre-deployed bridge contracts and elections should be run in same environment. Currently we use image "chainsafe/chainbridge-bootstrapped-celo" as bootstrapped nodes. This image was build be hands and includes celo nodes with deployed there chainbridge smart contracts. Deployment done with https://github.com/ChainSafe/chainbridge-celo/blob/main/e2e/deploy.go.
We should provide some workflow that build this image automatically when smart contracts being updated.
Implementation details
Testing details
Check that all is working
Acceptance Criteria
Script deploys contracts for celo-blockchain