David Mello

I think I am encountering something similar, but not necessarily with find, at least not directly. In my case I believe the tests seem to continue when it can't locate...

Hi @garg3133 any update on #4012 or this? It is causing major issues for us causing our test runs not to report results when unhandled errors happen in the suite...

Note in the attached zip in the original report it has the await keyword so you _will not encounter the issue_ unless you remove await from line 7 browser.page.googlePage().callWaitForever(); The...

So, maybe a silly question, but if the test is marked async does it require an await? browser.assert doesn't typically need to be awaited so now I'm confused.

So in async test cases is the recommendation to await every line or ensure at least one await is used?

This worked. I had to add the `/nightwatch/globals/*` and `/nightwatch/commands` to the exclude path, those contain .js files, to prevent a VS Code warning inside the tsconfig.json json about [files...

After, if I manually run `npm install chromedriver@latest` everything works. In previous revisions of create-nightwatch it installed chromedriver as a dependency during the init.

I forgot to mention I did try adding `await` in front of browser.waitUntil and/or the use of the command in the test and it does not help. 

Agreed, but after going through all sorts of different iterations and not having expected behavior I started second-guessing how this command maybe was supposed to work with async await, but...

@garg3133 thanks I will try the workaround. Can you also clarify since the custom command is async if the test using it needs to call it with await or if...