test: fix empty findAll results #11401
Merged
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
jcfranco
added
the
skip visual snapshots
jcfranco
requested review from
driskull,
eriklharper,
benelan,
Elijbet,
anveshmekala and
josercarcamo
eriklharper
approved these changes
Jan 28, 2025
github-actions
bot
added this to the 2025-02-06 - 3.0.0 Feb Breaking Change Release milestone
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.
Related Issue: #11398
Summary
This introduces a replacement to using
page.findAll/element.findAllto avoid false positives from asserting on empty results (e.g., assertions in a loop).Also, this will be enforced by the
no-restricted-propertiesESLint rule.