Problem (example):
We use an external test for a file-count in a (spool)folder. To ignore peak-moments, we use a "consecutive bad results" of 2 for the alert actions. (the test interval is 5 min)When there is a bad status, and 5 min. later, it's ok again, the good-status alerts are fired! (which I won't)
This wasn't a problem in 1,x, cause the retry-count was on the test itself, not on the alert actions.
Is there a way to solve this ?
Thus: only a good-status alert when there was a bad-status alert.
It works, except when the dependency bad action was fired (thus, when the bad count was exceed for that action). From that time, the good action is fired again ALWAYS(after a bad status).
(It seems there is a flag which is not reset after the good status alert was fired)
I tested v3.12 for 2 days, with almost 200 tests, and everything looks fine (for me). The dependency alert actions are ok now.
It's also a very good thing that you can modify mastertests on a multi-select.