-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
feat(ctb): Refactor L1 initializer tests #8198
Conversation
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #8198 +/- ##
===========================================
- Coverage 53.44% 53.35% -0.10%
===========================================
Files 162 114 -48
Lines 6040 3758 -2282
Branches 964 813 -151
===========================================
- Hits 3228 2005 -1223
+ Misses 2690 1677 -1013
+ Partials 122 76 -46
Flags with carried forward coverage won't be shown. Click here to find out more. |
Oddly enough, the gas snapshot for this test differs depending on the host architecture, tested on darwin aarch64 + linux x86_64. Omitting this from the gas snapshot. |
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.
The physiognomy of this regex checks out
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.
This looks great! Just some minor comments/questions
What do you think about also testing the L2 predeploys using this method? |
7e00716
to
2eb4a03
Compare
Overview
Refactors the
test_cannotReinitializeL1_succeeds
test to account for all L1 contracts which areInitializable
.The new test covers:
Initializable
contracts insrc/L1
are accounted for in thecontracts
array, giving us assurance that we have full coverage of L1 contracts' reinitializers._initialized
flag of each contract is properly set to3
at the start of the test, signifying that the contracts are initialized by the deploy script.initialize()
function of each contract cannot be called more than once - each attempt should result in a revert message of the formatError(string)
, with the message "Initializable: contract is already initialized".Metadata
Closes https://github.com/ethereum-optimism/client-pod/issues/214