action #119380
Updated by livdywan over 1 year ago
## Observation Context: When developing new test it's developer mode is very helpful. When needle update is needed, it can pause on mismatch and let you fix that and continue the test. But there is no similar option for `assert_script_run` failure, which even with manual single-step requires restarting the whole test on failure. This is especially frustrating when all that's needed is adjusted timeout (but the actual command worked). Feature: What I'd like, is an option to pause on failed `assert_script_run`. And then have at least an option to continue (ignoring the failure), or optionally retry the command (and pause again if it fails again). If retrying isn't an option, just pause and continue would be really useful, as one can inject commands via VNC manually. ## Acceptance criteria * **AC1:** Developer mode can stop on any individual module failure * **AC2:** marmarek is happy * **AC3:** Stopping on needle mismatches still works ## Suggestions - This new option could be implemented by creating a new lower level pause($reason) backend command and just send that on module failure (but before the post_fail_hook) if "pause on module failure" is enabled, or a module_failure($module) to have the backend decide what to do.