Lessons Learned from Test Failures due to a new ChromeDriver Bug

@download_path = File.expand_path File.join(File.dirname(__FILE__), "..", "tmp")
prefs = {
:download => {
:prompt_for_download => false,
:default_directory => @download_path
@driver = Selenium::WebDriver.for :chrome, :prefs => prefs
  1. Web test automation depends on browsers, i.e, mostly Chrome. Chrome (and its driver) updates regularly, be prepared with changes.
  2. Run your full regression testing often (daily), so that you know the tests/code/env statuses well. When unexpected test failures occur, you will be more likely to handle them calmly and narrow down the cause quickly.
  3. Even for people who are getting used to the real Agile way of software development: releasing new updates to production on green builds, the importance of test automation, and continuous testing is still under-appreciated.
  4. Act quickly and proactively, e.g. searching Selenium Github issues or raising one there.
  5. Reverse your infrastructure if necessary, in this case, re-install an old version of Chrome in the interim.

Award-winning software developer, test automation & CT coach, author, and speaker. Help teams succeed with Agile/DevOps by implementing real Continuous Testing.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store