suppressNotFoundErrors property in the new Element API should ideally only suppress the NoSuchElementError but instead it suppresses all the errors that the WebDriver encounters and returns while trying to find the element.
For example, it also suppresses the InvalidSelectorError, which is thrown when the selector passed to the find() command is invalid, which could be a human error while writing the test.
Description of the bug/issue
suppressNotFoundErrorsproperty in the new Element API should ideally only suppress theNoSuchElementErrorbut instead it suppresses all the errors that the WebDriver encounters and returns while trying to find the element.For example, it also suppresses the
InvalidSelectorError, which is thrown when the selector passed to thefind()command is invalid, which could be a human error while writing the test.Steps to reproduce
In any test, run the following command:
The above command will suppress and not throw any error even though the error is
InvalidSelectorErrorand notNoSuchElementError.Sample test
No response
Command to run
No response
Verbose Output
No response
Nightwatch Configuration
No response
Nightwatch.js Version
latest
Node Version
No response
Browser
No response
Operating System
No response
Additional Information
No response