test(trie): fix nonexistent edge keys test name - #7250
Open
fmterrors wants to merge 1 commit into
Open
Conversation
Signed-off-by: fmterrors <fmterrors@outlook.com>
github-actions
Bot
added
the
external-contributor
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
1 participant
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.
Motivation
The range-proof property test misspells “nonexistent” in its function name and uses an ambiguous sentence in the adjacent comment. Accurate test names make failures and filtered test runs easier to interpret.
Description
Rename
proptest_verify_range_nonexistant_edge_keystoproptest_verify_range_nonexistent_edge_keysand clarify that both boundary keys are absent. The generated cases and assertions are unchanged.cargo fmt --all -- --checkpasses.Checklist
STORE_SCHEMA_VERSION— not applicable; storage and schemas are unchanged.Closes N/A