How can we prevent test steps from being skipped if a test step before fails

[Golshy]

Suppose I have a test case with the following steps:

1. I am on the website
2. I click on wishlist
3. I validate number of items in wishlist
4. I navigate to product PDP
5. I add the item to shopping bag

If step #3 "I validate number of items in wishlist" fails, the remainder of the steps should not be skipped. Rather, the script should attempt to proceed.

If step #4 "I navigate to product PDP" fails, then it is appropriate for the remainder of the steps to be skipped, as step #4 is critical functionality and must critical fail all the time.

Thus, is there a way to integrate a Soft fail vs a Hard fail in NightWatch?

So far we have attempted to add skip_testcases_on_fail: false, into our nightwatch.conf.js in the test_settings:{} , but it our test case still aborts after a single test step failure.

Any help would be greatly appreciated!

[beatfactor]

You can try using .verify instead of .assert. It has the same apis, but in case of a failure verify will continue the test of the testcase. The test will still be marked as failed at the end.

[Golshy]

Hey Andrei,

Thanks for the response.

I see the "Time out" failure in the console logs, but it doesn't translate over to the cucumber reports that get sent at the end of the test script. The steps with .verify still are marked as passed, even if they encounter a fail.

Would this be something to be fixed on the cucumber report side of things?

[beatfactor]

I would need to see more details before I can say for sure. Which version of Nightwatch are you using?