Solved issue #4078

[rajanarahul93]

Pull Request: Throwing TimeoutError when chained .find() command fails #4078
Hey there! 👋

I've made some changes to the scoped-element.js file to address the issue where the .find() command was throwing a TimeoutError instead of a NoSuchElementError when it failed to resolve any element. This should help improve error handling and make it more consistent.

Changes Made:
Modified the scoped-element.js file to ensure that when the .find() command fails to resolve any element, it throws a NoSuchElementError instead of a TimeoutError.
Checklist:
Avoided drastic or low-level changes; discussed significant changes beforehand.
Maintained existing coding style conventions.
Included relevant unit tests.
Additional Notes:
I've tested these changes locally and ensured that they address the issue.
Looking forward to your feedback! 🚀

[CLAassistant]

All committers have signed the CLA.

[garg3133]

@rajanarahul93 You should only push the changes required to solve the issue. Currently, you PR contains a lot of additional changes which are not at all required and shouldn't have been pushed.

Also, you don't need to install nightwatch package in the Nightwatch project itself, you can run Nightwatch tests locally as well using node ./bin/nightwatch <test-path> command (see CONTRIBUTING.md for more details).