-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multisubnet test #736
Multisubnet test #736
Conversation
executeTopDownMsgs(msgs, nativeSubnetName, address(nativeSubnetGateway)); | ||
|
||
// works with no state changes | ||
assertEq(recipient.balance, amount); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this test would be easier to understand this test if it started with
- recipient/parent having balance=3
- caller/child having balance=0
This way the reader could imagine that the initial state of the tests is when the child released its balance completely.
|
||
executeTopDownMsgs(msgs, nativeSubnetName, address(nativeSubnetGateway)); | ||
|
||
require(caller.balance == amount + amount, "refund not happening"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above about initial balances as this amount + amount
assertion is a bit confusing now.
Closes ENG-747
Adding more multisubnet test cases.