You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we use await browser.assert.<some-assertion> inside other commands like a custom-command (see #3286) or inside debug interface, the promise for the assertion is never resolved and the test gets stuck after the assertion.
Please note that the assert command currently works correctly inside the debug() interface because of a workaround (we replace assert with verify) but this needs to be fixed as we'll revert the workaround once #3275 is merged.
The text was updated successfully, but these errors were encountered:
Actually asserts are not designed to use with await. async/await is Nightwatch to get the values from Nightwatch commands and assert commands never return a value. We can have a look if we can make this work
Actually asserts do return a value. Like if browser.assert.title() is called, value of browser.title() (that is, the command executed as part of performing assert) is returned back.
If we use
await browser.assert.<some-assertion>
inside other commands like a custom-command (see #3286) or inside debug interface, the promise for the assertion is never resolved and the test gets stuck after the assertion.Please note that the
assert
command currently works correctly inside thedebug()
interface because of a workaround (we replaceassert
withverify
) but this needs to be fixed as we'll revert the workaround once #3275 is merged.The text was updated successfully, but these errors were encountered: