You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, by default, if some assertion fails, all remaining TestSteps are skipped. Would be nice to add flag (on test_settings level and be able to override on module level) that would change such behavior.
Ex. let's assume we have 5 TestSteps in one module.
Step1: works ok
Step2: throw exception
Step3: browser.verify fails
Step4: browser.assert fails
Step5: works ok
In current nightwatch version, steps 1-4 are executed and Step5 is skipped. After adding such flag ("continue_testSteps_after_failure"?) Step5 would be executed as well (Browser.verify does similar thing, but it doesn't break current TestStep execution)
The text was updated successfully, but these errors were encountered:
MateuszJeziorski
changed the title
Not skip TestSteps after assertion failure
Not skip TestSteps after assertion fails
May 25, 2015
Now, by default, if some assertion fails, all remaining TestSteps are skipped. Would be nice to add flag (on test_settings level and be able to override on module level) that would change such behavior.
Ex. let's assume we have 5 TestSteps in one module.
Step1: works ok
Step2: throw exception
Step3: browser.verify fails
Step4: browser.assert fails
Step5: works ok
In current nightwatch version, steps 1-4 are executed and Step5 is skipped. After adding such flag ("continue_testSteps_after_failure"?) Step5 would be executed as well (Browser.verify does similar thing, but it doesn't break current TestStep execution)
The text was updated successfully, but these errors were encountered: