-
Notifications
You must be signed in to change notification settings - Fork 374
Added discussion on how and when to use cheat codes #257
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
Conversation
0xPhaze
left a comment
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 would further include the example of vm.mockCall. Imo it is a big red flag if seen in tests. It has similar issues to vm.prank, however it further completely bypasses any business-logic and can easily break assumptions.
I think this should be part of another document on good testing practice, so we can discuss cheat codes that are not implemented in hevm/echidna. |
|
This one looks ready for another review or merging @montyly |
No description provided.