-
Georges Racinet authored
This is a preliminary for any CI attempt, since installing the webdriver inside a Docker container is a long and error prone process. This will allow to use a separate service image such as `selenium/standalone-chrome` and that may also turn to be a good option even outside Docker-based CI contexts. The new `Heptapod.new_webdriver()` method is now the unique one to be called to create new drivers, a preliminary to be able to run the tests with other drivers anyway. In particular, this should come handy if installing chromedriver is a problem.
90fc419eedf0