Nightwatch: abortOnAssertionFailure not taken into account for .verify assertions

[Zaents]

'verify' command work incorrect on version Nightwatchls newest than 0.9.20. That is it work as a 'assert' command and stop running test step when fail. It is tested on one script on v.1.0.18(19) and on v.0.9.20.
Verify-command run correct only on v.0.9.20 and oldest with same config-files.
I've attached Logs of nightwatch's run to this task. I see that in new version after 'verify' failed we immediately get into step 'afrerEach', and then step 'after' was called and it's produce the 'end' method.
It's very big problem because 'verify' command used for mass validating data such a web-analytics, etc. , when all failed verification must be run and test must be run to the end.

I see in documentation these words - "
The classic assert/verify library is still available on the Nightwatch instance as two objects containing the same methods to perform assertions on elements:

.assert - when an assertion fails, the test ends, skipping all other assertions.
.verify - when an assertion fails, the test logs the failure and continues with other assertions."
So, it doesn't work in current version.

[Zaents]

`const fs = require("fs");

module.exports = {
'@tags': ['tests1'],
'test': function (browser) {
browser.verify.equal(1,2,'EQUAL TEST!!!!')
browser.verify.equal(2,5,'SECOND EQUAL TEST!!!!')
}
};
`
v.0.9.20

v.1.0.19

[stalex90]

+1

[beatfactor]

Please avoid posting screenshots as verbose logs and try to post the logs inline.

[eternityCoder1]

@beatfactor Any update on this? I am having same issue in my project as well. Looking forward for the the fix. Greatly appreciated the promptness in fixing this.

[RajaBellebon]

+1, I am facing this issue since I updated to the latest version.

Thanks in advance!

[beatfactor]

This should be fixed in v.1.1.0.

[RajaBellebon]

@beatfactor thanks for this - when do you plan to release this version on npm?

Cheers!

[beatfactor]

@RajaBellebon Next week