memihai

@asos-saveriocutrupi I hit that error too but that one hangs the process indefinitely. I never logged it as I didn't know how to reproduce it. There are 2 differences between...

I played around with this today and realised that if I define the command like this ``` commands: [ { async waitForAnElementToBeVisible() { //this.expect.element('@randomXpath').to.be.visible; await this.customWait(xpath.randomXpath('Random string')); } } ],...

The problem described here is still an issue in Nightwatch 3.0.1, I just tested it today. @ituradastra FYI.

@gravityvi, @AutomatedTester Do you have any updates on this? We want to resume our efforts to migrate to NW3 now and this is a blocker for us.

@gravityvi yes your solution works for that example but what if I want to click the element after waiting for it to be visible ``` waitForAnElementToBeVisible() { this.customWait(xpath.randomXpath('Random string')); return...

@beatfactor, using the NW runner doesn't stop execution. To the default NW project installed with "npm init nightwatch" I added the below as follows: //nightwatch/page-objects/google/search.js ``` const searchCommands = {...

@humphreyn If you are migrating a framework you might also be interested in [this](https://github.com/nightwatchjs/nightwatch/issues/3596) issue. This one is my blocker and you might hit it. I am also migrating a...