fix: assertion failure in new Elem API leads to unhandledRejection.

[garg3133]

Right now, if we create a test case using an async callback but do not use await anywhere inside the test case, failure of the newly introduced assertions in the new Element API leads to unhandledRejection:

it('asserts using newly introduced assertions', async function(browser) {
    browser.navigateTo('https://duckduckgo.com');

    browser.element('input[name=q]').assert.not.visible(); // it should fail normally but leads to unhandledRejection
    browser.element('input[name=q]').getText().assert.contains('Search');
});

With this PR, assertion failures will gracefully end the test instead of raising unhandledRejection which abruptly ends the test run.

Caveat

If we use then() with the assertion promises, assertion failure leads to unhandledRejection. But using then() inside an async function is not common, nor is using then() on any normal Nightwatch command or assertion.

it('asserts using newly introduced assertions', async function(browser) {
    browser.navigateTo('https://duckduckgo.com');

    // using `then()` on NW commands/assertions is not recommended
    browser.element('input[name=q]').assert.not.visible().then((res) => console.log(res));
    
    // use like below instead
    const res = await browser.element('input[name=q]').assert.not.visible();
    console.log(res);
});

[github-actions]

Status

• ❌ No modified files found in the types directory.
  Please make sure to include types for any changes you have made. Thank you!.