-
Notifications
You must be signed in to change notification settings - Fork 332
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
fix(tests): Conform to upcoming expectRevert
behavior
#379
Conversation
Should be good to go now! @mds1 |
394efef
to
9db38e6
Compare
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.
Sorry missed that this was ready, thanks @Evalir! Looks like CI is passing—am I correct that this can be merged now (without waiting for v1 release) since this fix is compatible both with current and future (v1) expectRevert behavior?
Yep indeed can be merged now! |
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.
Thank you!
Followup to foundry-rs/foundry#4945
The new expectRevert behavior means that it will only check the next call, instead of checking a revert at the "test" level. Some of the tests in
forge-std
expected the latter behavior, but with the linked PR this will change. This updates the tests to comply to the new behavior.