Approach
Following the issue's comment made by @kwinkunks
"But we could mark tests requiring the driver, however, so that if situations like this happen again, we can easily turn off the tests temporarily.", the approach went on marking the tests that requires dash / Selenium as "browser-test", which can be skipped with the command "pytest -m --skip-browser-tests". I also added a validation for the webdriver importing so it can also be skipped automatically running the "pytest" command without args when the chromedriver is missing in PATH, following the approach of Equinor/ERT's tests when some simulators are not available.
Issue Resolves #446
Approach Following the issue's comment made by @kwinkunks "But we could mark tests requiring the driver, however, so that if situations like this happen again, we can easily turn off the tests temporarily.", the approach went on marking the tests that requires dash / Selenium as "browser-test", which can be skipped with the command "pytest -m --skip-browser-tests". I also added a validation for the webdriver importing so it can also be skipped automatically running the "pytest" command without args when the chromedriver is missing in PATH, following the approach of Equinor/ERT's tests when some simulators are not available.
Pre review checklist