potatoeggy/rooster

Selenium error handling

Closed this issue · 1 comments

If Selenium breaks at some point (e.g., a slow internet connection leads to elementnotfound), this should be caught and retried I'd say three times before sending for help.

Additionally, if authentication fails that needs to be noted too.

This was largely fixed in the rewrite with Timeout and InvalidSessionId exception handling.