-
Notifications
You must be signed in to change notification settings - Fork 335
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
chore: conform test naming to style guide #433
Conversation
Sorry what do you mean by this bolded part? Also just to clarify, the |
This is great, thanks @Sabnock01! Just about ready to merge, but want to bump the question in #433 (comment) first |
Ah, no problem. I was trying to say that specific syntax didn't appear necessary for any of the current tests but I don't recall specifically why I worded it the way I did. |
Ah got it. Yea of course it’s not strictly necessary, but since we’re updating to follow the best practices doc conventions we may as well use that one too, for tests that are focused on checking revert conditions. Would you mind using that where applicable? |
Sure, can do that. |
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.
Thanks so much!
This PR puts the
forge-std
test naming conventions in line with the style guideSome liberties have been taken with respect to the names in
StdAssertions.t.sol
but open to any feedback.I did not add any test names with the
Revert[If|When]
modifier since none of the tests appear to pass or fail conditionally. Correct me if this is erroneous.Closes #273