Hardcode chromedriver version until we get an upgrade that works

[soniaconnolly]

Chromedriver versions are behind Chrome, so we need to hardcode the version until Chromedriver catches up.

This is affecting more and more devs who want to run feature specs, and it's a hassle to keep an edited rails_helper.rb around without committing it. We can revert this when we get a version of Chromedriver that works.

ETA: Looks like we need to upgrade the version of Chrome that CI uses to make this work. Is that an option?

[aduth]

ETA: Looks like we need to upgrade the version of Chrome that CI uses to make this work. Is that an option?

We probably could (should even?). I can't recall if that's as easy as just getting a "fresh" CI image SHA from devops (e.g. bottom of the build log here) to use in config, or if it needs something else.

Alternatively, we could maybe isolate it to local development, either using the ENV['CI'] flag, or explicitly catching the error and falling back?

require 'webdrivers'

begin
  Webdrivers::Chromedriver.latest_version
rescue Webdrivers::VersionError
  Webdrivers::Chromedriver.required_version = '114.0.5735.90'
end

[soniaconnolly]

we could maybe isolate it to local development, either using the ENV['CI'] flag

That works much better, thanks! I thought about that too after walking away from the computer on Friday.

[aduth]

LGTM 👍

[aduth]

I might expect to see this configuration someplace like support/capybara.rb, but not a big deal if it's short-lived.

[soniaconnolly]

Good idea. That works too. No need to reset it before each spec.

[timothy-spencer]

If this gets you going, LGTM! Longer term, we should move the IDP CI build over here so that you have direct control over it and don't need to hack in stuff like this.