Closed ZScannell closed 1 year ago
Hey @ZScannell, thanks for raising this issue. skip_testcases_on_fail
determines whether to skip the test cases after the previous test case has failed. I think in this case to keep the commands running after a failure we can replace assert
keyword with verify
. Verify will still report errors but will not stop executing subsequent commands. Let me know if this works
Hello @gravityvi - I just re-ran the above sample test using verify
instead of assert
and can confirm that it is operating as expected now. I am closing the issue with the comment. Thank you for your help!
Description of the bug/issue
Once a test fails, I'd like the test suites to continue running so that I can see all errors at once rather than having to sift through them one at a time.
I can do this by setting
skip_testcases_on_fail: false
inside the nightwatch.conf.js file.This is on the latest version 2.6.1.
Steps to reproduce
npm init nightwatch@latest
(from https://nightwatchjs.org/guide/quickstarts/create-and-run-a-nightwatch-test.html)skip_testcases_on_fail: false
to thetest_settings
json inside of nightwatch.conf.js.npm nightwatch .\test\reducedTestCase.js
.Sample test
Command to run
Verbose Output
Nightwatch Configuration
Nightwatch.js Version
2.6.1
Node Version
18.13.0
Browser
Firefox 108.0.2; Chrome 109.0.5414.75
Operating System
Windows 10 Pro 19044.2364
Additional Information
No response