browser.assert breaks the run of the next tests

[ymatviikiv]

Hello, I run many tests with a common tag.
I have a problem with browser.assert*. When a test fails, the next one doesn't start. No report about the current (failed one), so hooks don't work. I tried to play with abortOnAssertionFailure: false (set it in nightwatch.conf.js or in globals.js) - the same result.
In my case, I'm just checking the equivalence of 2 values (like browser.assert.equal(2, 1)).
How to get a failed result on that and not break the run of the next tests?
Thanks in advance.

[jmervis99]

HI!
I think assert stops tests and expect lets them continue on failure.

[ymatviikiv]

Thanks @jmervis99 for your answer.
It is, like you have mentioned. The same in documentation - https://nightwatchjs.org/guide/writing-tests/adding-assertions.html#overview
I want the failed test result of the assertion. But only for that one test. The rest should run in there order.

[ymatviikiv]

From my investigation, the problem is related to callbacks.
Because when I use the simple example
await browser.assert.equal(2, 1)
in the code, it works fine.

In the same time, when I do something like:

await browser.getText(selector, (result) => {
    const selectorText = result.value
    browser.assert.equal(result.value, "some text")
})

it fails with that error: NightwatchAssertError
One of the solutions is to add async before (result).

We are doing a migration from version 0.9 to 2.x. Is it possible to add a failed result to such errors (to fix the failed ones but not break all the runs)?