Consider adding a verbose argument that may be used to assist in troubleshooting some of the otherwise difficult to identify issues when they arise. When we come across issues we seem to be temporarily building verbose prints into output -- would probably save us some effort if we do this once to stop re-inventing the wheel every time we need to troubleshoot
Optional argument:
--verbose
Code changes:
In various places in code & especially where selenium errors are handled non-fatally, pass explicit errors back to stdout if --verbose is true
Consider adding a verbose argument that may be used to assist in troubleshooting some of the otherwise difficult to identify issues when they arise. When we come across issues we seem to be temporarily building verbose prints into output -- would probably save us some effort if we do this once to stop re-inventing the wheel every time we need to troubleshoot
Optional argument: --verbose
Code changes: In various places in code & especially where selenium errors are handled non-fatally, pass explicit errors back to stdout if --verbose is true