I've been thinking about how to fail an Automation Framework plan early, for example if the authentication fails.
My plan is to create a new "monitor" type of job test.
It would be similar to the "stats
" job test but instead of running after a job it would run _during_ a job.
It would only be supported by specific 'long running' jobs like the spider, spiderAjax, active scan etc
config would include a statistic name and a threshold - if that
threshold is exceeded at any point during the job then the job will
fail. The action being performed (spider / active scan etc) will be stopped.
Whether or not the plan fails will depend on the plan config.
idea is that this could then be used to check for things like auth
failures and exit a job/plan early rather than potentially waiting
hours for it to finish and then fail.
Any thoughts, suggestions or feedback?