test: extend storage layout tests with CoveredVaultWrapper checks - #114
Merged
Conversation
dB2510
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Low risk: test-only change that adds an additional storage layout regression check; main impact is potential CI failures if the pinned baseline is incorrect or storage output format changes.
Overview
Extends
StorageLayout.t.solto pin and assert the storage layout ofCoveredVaultWrapper(38 expected entries), guarding against slot/offset/type drift across its deep inheritance chain.Updates the test’s documentation to explicitly include
CoveredVaultWrapperas a defensive baseline alongside the mainnet-deployed upgradeable proxies.Reviewed by Cursor Bugbot for commit 9799ae4. Bugbot is set up for automated code reviews on this repo. Configure here.