Add migration E2E test and relevant tooling. #61
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e testnode infrastructure to support adding this part to the test.
…ring the migration test. Also adds an option to write the switchDelayThreshold in the config.
…hanges get merged into the nitro integration.
…pts that help for verifying recent chain config changes are working after running the migration test.
…de into set-chain-config
…helper scripts for reviewers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #60
This PR:
Adds the tooling needed to support a migration test in the nitro testnode, and the majority of the migration test itself.
This PR does not:
Implement the full migration test. Remaining work includes verifying via the test script that transactions are appearing in the espresso dev node.
Key places to review:
Changes to
migration-test.bashas well as the associatedcreate-espresso-integrated-nitro-node-from-local-tag.bashandcreate-espresso-integrated-nitro-node.bashscriptsI have been using the
create-espresso-integrated-nitro-node-from-local-tag.bashscript to run the test with locally built nitro docker images with the recent chain config changes. Once those changes merge, I intend to remove that script and again pull an image built from the integration branch.In addition after the migration-test.bash script finishes, you can run the
transaction-sender.bashscript in the top level of the repo to send several transactions to the test-node, and then runtransaction-fetcher.bashto iterate through the first 1000 views and see if transactions have made it from the nitro node to the dev node.