QE-17615 Track and log how fuzzy finds elements #560
Conversation
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
ddl-kgarton
requested review from
juwatanabe and
ddl-kavya
and removed request for
a team
ddl-kgarton
force-pushed
the
log-fuzzy-label
branch
2 times, most recently
from
0d7009f to
fc43761
Compare
ddl-kgarton
force-pushed
the
log-fuzzy-label
branch
from
fc43761 to
144fa5e
Compare
ddl-kgarton
force-pushed
the
log-fuzzy-label
branch
from
144fa5e to
fd19dd2
Compare
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.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Fuzzy operates in a completely opaque way, providing no information to the end user on how it selects which element to interact with.
Issue Number: https://dominodatalab.atlassian.net/browse/QE-17615
What is the new behavior?
Track which elements are found with which type of selector in Fuzzy, and communicate that back to cucu so it can log the general form of the selector that was used to retrieve the element from the DOM.
Does this PR introduce a breaking change?