(NFC) dev/core#2029 - Make assertions in PrevNextTest more skimmable #18822
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.
Overview
The test appears to have a random failure. Making it more readable may help figure out why.
Before
testDeleteByCacheKey()
and the relatedtestFillArray()
both have some assertions in these two forms:After
The verbose form is replaced with the pithier form.
In the pithier form, some of the default inputs are made explicit.
Comment
It is confusing that the method
getSelections()
has a parameter$action
which can beget
orgetall
-- and thatgetall
does not (in fact) return selections. It returns all! (The fact that the contract is weird makes the unit-test helpful imho...)