After a scenario failure, cucumber-nightwatch stops running the remaining scenarios

[sharathkonda]

I got 5 scenarios in a feature.

If the 3rd scenario is failed, the runner stops and doesnt' continue to execute the remaining scenarios in that feature file.

[mucsi96]

Thanks for feedback!

This is the expected behavior. See Nightwatch.js assertions
Can I close this issue?

[ivancho98]

Actually, it is possible that @sharathkonda is using .verify, in that case the runner should not stop.

[mucsi96]

@sharathkonda are you using .verify for assertions?

[sharathkonda]

I use in my common library the nightwatch assertion.

this.api.assert.visible(selector);

On 4 February 2016 at 10:13, Igor Muchychka notifications@github.com
wrote:

@sharathkonda https://github.com/sharathkonda are you using .verify for
assertions?

—
Reply to this email directly or view it on GitHub
#28 (comment)
.

[mucsi96]

Try to replace assert with verify. This way when an assertion fails, the test logs the failure and continues with other assertions.

[rohitkashyapvatta]

This is happening in our case as well, the test step failure , fails the other scenarios of the suite with same error "at World. (/home/jenkins/workspace/.............................)" . Can you please advise what is happening here?

[JoseThen]

I am seeing the same as well, using : client.verify.elementPresent(elements) within a loop, stops once it fails and does not continue with the rest of the elements in the loop.