test: increase StakeRegistry test coverage
#400
Conversation
This file contains 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
added 10 commits
February 13, 2025 12:13
tsnewnami
changed the title
StakeRegistry test coverage
tsnewnami
force-pushed
the
james/stakeregistry-coverage
branch
from
e397776 to
da25414
Compare
tsnewnami
changed the title
StakeRegistry test coverageStakeRegistry test coverage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR extends the test coverage of the
StakeRegistry. Specifically targeting coverage over the following functions:getStakeHistorygetStakeHistoryAtIndexsetSlashableStakeLookAheadFuzzing unit tests have been for each of the above as well as including
getStakeHistoryandgetStakeHistoryAtIndexinto the fuzzing operator registration and deregistration tests.