-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supress error for chained .find()
command
#4079
Comments
I was considering resolving this issue by removing the elements with the same shared |
8 tasks
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug/issue
Further chained
.find()
commands should not throw the Timeout or any other error again. Ex. inbrowser.element('.invalid-selector').find('selector').getText();
, there should only be one error due tobrowser.element()
and.find()
should not throw an error again (suppress the error for it).Branched off from issue: #3991
Reference comment: #3991 (comment)
Steps to reproduce
No response
Sample test
No response
Command to run
No response
Verbose Output
No response
Nightwatch Configuration
No response
Nightwatch.js Version
3.3.7
Node Version
No response
Browser
No response
Operating System
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: