Omit webdrivers gem from Gemfile template

[seanpdoyle]

Motivation / Background

As of Selenium 4.6, the Selenium Manager is capable of managing Chrome Driver installations and integrations. As of Selenium 4.11, the
Selenium Manager is capable of capable of resolving the Chrome for
Testing installation path.

Detail

By omitting the gem declaration from the Gemfile.tt, newly generated applications and applications updating their Gemfile in lockstep with newer Rails versions can shed the dependency and avoid test failures introduced by newly released Chrome versions (like, for example, titusfortner/webdrivers#247).

Checklist

Before submitting the PR make sure the following are checked:

• This Pull Request is related to one change. Changes that are unrelated should be opened in separate PRs.
• Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: [Fix #issue-number]
• Tests are added or updated if you fix a bug or add a feature.
• CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.

[simi]

Wouild it make sense to ensure selenium-webdriver 4.6+ gem is installed in Gemfile?

[seanpdoyle]

Wouild it make sense to ensure selenium-webdriver 4.6+ gem is installed in Gemfile?

That's a great idea. I've changed both Rails' development Gemfile (the one you've linked to here) as well as the Gemfile.tt template file to specify >= 4.6.0.

[titusfortner]

It should be Selenium 4.11 (not yet released) because while 4.6 - 4.10 manages drivers, it does not support the new Chrome for Testing location for chromedriver 115+.

[seanpdoyle]

@titusfortner thank you for providing that context!

I'd like to note that CI was passing when locking to version 4.6, but will fail indefinitely until Selenium releases 4.11.

I'm now subscribed for those releases, so I'll come back to ping this PR once that occurs (@titusfortner I'll be you're also patiently watching and waiting, so don't hesitate to ping this PR if you beat me to it).

[seanpdoyle]

@titusfortner there is a 4.11 Selenium release. I've bundle installed and force-pushed this branch to kick off CI.

[guilleiguaran]

Looks like we need to use a lower version for Ruby 2.7:

Could not find compatible versions
--
  |  
  | Because selenium-webdriver >= 4.9.1 depends on Ruby >= 3.0
  | and Gemfile depends on selenium-webdriver >= 4.11.0,
  | Ruby >= 3.0 is required.
  | So, because current Ruby version is = 2.7.8,
  | version solving has failed.

[seanpdoyle]

@guilleiguaran thank you for sharing that, that's good information! That's unfortunate that there is a Ruby version requirement attached to Selenium's Ruby bindings.

It's probably a discussion worth having outside of this branch, but Ruby 2.7 is end-of-life as of 2023-03-31.

Since these changes are focused on template files for new applications' test suites, I wonder if there's a way to work around Rails' support for 2.7.

[titusfortner]

Selenium supports what Ruby supports, and I'll strongly defend that as a feature and not a bug for any and all Ruby open source projects.

Alternately, webdrivers 5.3 now has support for chromedriver 115+ and still works for Ruby 2.7
The downside is that it restricts Selenium 4.11+ and gives a post_install_message
That might be better at this point, though?

[rafaelfranca]

We can't drop support to old rubies without bumping the major version of Rails. We are not going to bump the major version of Rails for the next release so we need to support Ruby 2.7.