- "invalid literal for int()" error in exec_time calc, i.e., case of early fail caused by network issues
- UNKNOWN status for failed suites with no reported failed tests, case as above
- codding style, wrap long lines
- doc update: README Performance metrics section
- container stop (autoremove) on interrupt (SIGINT/ SIGTERM)
- parse runner console output (SeleniumIDE
echo
command) for additional perfdata marked withPERFDATA:
prefix and guidelines compliant for Performance data, i.e.,PERFDATA: First Response Time = ${calculatedTime}s;${warningThreshold}
- catch-all for exceptions exit codes, as by the guidelines Plugin Return Codes
no-newlines
option that prints newlines literally on multiline output, useful for passive check Passive Check- failed and passed perfdata thresholds for consistency with result status
- configurable timeout option
- support for container with alternative browser
- verbose option for more Nagios Guidelines compliant error output
- calculate exec_time based on execution all tests in all suites from all side files
- aggregated passed, failed, and total counters for all tests
- process and support more than one side file, issue osdis/check_selenium_docker#6
- exec_time calculation error in the absence of tests, issue osdis/check_selenium_docker#5