Retry Count setting should have greater priority over Error Behavior setting or we need a new Behavior setting
In reference to this URL:
When the Error Behavior setting is set to STOP and the retry count is NON-zero, when a minor test error happens I feel that the retry count should be honored and if all the retries have been exhausted only then should all testing STOP per the behavior setting.
Currently (v8.3.0 and lower) this is not the case and if you set retry to > 1 the test will just STOP on the 1st error it hits with no attempted retry.
I would like to see the ability to bump the retry count setting as a higher priory action OR add a new behavior setting called “STOP if no Retries” which could also achieve my goal here without braking the current Ranorex behavior for others who may require it that way.