waitUntil throws error if the element on which it is used does not exist

[garg3133]

Description of the bug/issue

waitUntil should instead not run at all if there is no element to wait for (element.find() command already waits for the element to be present and then only it passes over to waitUntil).

Steps to reproduce

Go to any test and write browser.element.find('<some-invalid-selector>').waitUntil('visible');

Sample test

No response

Command to run

No response

Verbose Output

No response

Nightwatch Configuration

No response

Nightwatch.js Version

3.0.1

Node Version

No response

Browser

No response

Operating System

No response

Additional Information

No response

[gravityvi]

waitUntil is an assert type. Assert will throw NightwatchAssertError on failure

[garg3133]

@gravityvi Yes, it should throw a NightwatchAssertError, but what I'm complaining about is the 500 error messages above the NightwatchAssertError.

Ideally, if the element itself is not present (which we can find just by looking at the result of element.find command), we shouldn't go on to find if the element is visible or not (by running waitUntil('visible') command), but just throw the NightwatchAssertError straightaway.

(And also, the NightwatchAssertError should be but got: "not present" instead of but got: "not visible".)