Reasons for documenting this, rather then silencing the error:
(1) Errors should never pass silently.
(2) Unless explicitly silenced.
(3) I want the user to make a choice about whether he wants to retry making
the screenshot or whether he doesn't care for it.
(4) I don't want to re-invent Robot Framework's machinisms for retrying and
silencing errors
This gives a specific error message for the backend's explicit
"Screenshot not available" status, so one can handle it in the test script.
memcmp
commented
11 years ago
Reasons for documenting this, rather then silencing the error:
(1) Errors should never pass silently. (2) Unless explicitly silenced. (3) I want the user to make a choice about whether he wants to retry making the screenshot or whether he doesn't care for it. (4) I don't want to re-invent Robot Framework's machinisms for retrying and silencing errors
This gives a specific error message for the backend's explicit "Screenshot not available" status, so one can handle it in the test script.