Add fork tests for flow rate controls #85
Merged
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
📃CI ReportCompiling 143 files with 0.8.19
For a full HTML report run: |
wcgcyx
reviewed
Feb 2, 2024
wcgcyx
approved these changes
Feb 7, 2024
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.
This PR introduces fork tests to check the flow rate control capabilities of the bridge, a crucial security feature. Despite the existence of numerous unit and integration tests for this function, it's necessary to test it against a deployed version of the bridge. Here, parameters, configurations, and token contract idiosyncrasies could potentially affect its functionality. However, running live E2E tests on the flow rate control feature on mainnet isn't feasible. Hence, these tests serve as an alternative way to confirm that this capability works as expected under a range of conditions, in all bridge deployment environments.
This PR addresses SMR-2336-SMR-2238