Open
Conversation
|
I had to do some like this: |
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
2 participants
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.
Google's search has a drop-down that is automatically triggered when searching, with suggestions.
That drop-down hides the 'btnG' button so the test outputs an error saying that the element is not visible.
I tried to select the first Google's suggested element, but the suggestion is all lowercase, so the "seeInTitle" fails (unless is also changed...).
I also tried to use the same selector (element's name q) instead of the id #lst-ib for clarity but it doesn't work.
If you want to keep the click function for demonstrative purposes, a solution is to press the ESCAPE key in order to close the drop-down and then click on btnG.