Unhandled rejection while using expect assertions in an async test step

[sarahRaafat15]

Describe the bug

After an expect element to contain text assertion fails in an async step, test stops the rest of the execution, also the results object 's modules is empty.

Sample test

sampleTest.js

// Please add the sample test here

 it("async step", async function(browser) {
      browser.url("https://nightwatchjs.org/")
      browser.expect.element('#navigation').text.to.contain("someText")
    })
    it("2nd step", function(browser) {
      browser.url("https://google.com/")
    })

Your Environment

Executable	Version
nightwatch --version	2.0.10
npm --version	8.3.1
node --version	v16.14.0

Browser driver	Version
chromedriver	98.0.0

OS	Version
Windows	10

[gravityvi]

Hey @sarahRaafat15, even in the case of sync test methods rest of the tests are skipped and this is the expected behavior

[sarahRaafat15]

Hi @gravityvi , but in the case of having
skip_testcases_on_fail: false in nightwatch.json it should not.
Also I think this is a duplication of this bug #3075 which is solved in nighwatch 2.0.8 so it should not be occuring in 2.0.10 ?

[gravityvi]

Thanks @sarahRaafat15 for reporting this. I have noticed this only happens while using browser.expect assertions. We will look into this.