[🐛 Bug]: Selenium Manager not working on FreeBSD

[gdonald]

What happened?

I have selenium-webdriver 4.15.0 installed in a Rails application. I have RSpec configured to use :selenium, which I understand to mean firefox/geckodriver, not chromedriver:

RSpec.configure do |config|
  config.before(:each, type: :system) do
    driver = :selenium
    driven_by(driver)
  end
end

When I remove the selenium cache, and re-run my system spec, a new chromedriver is downloaded instead of the geckodriver.

> tree ~/.cache/selenium
/Users/gd/.cache/selenium
├── chromedriver
│   └── mac-arm64
│       └── 119.0.6045.105
│           └── chromedriver
└── se-metadata.json

4 directories, 2 files

> rm -rf ~/.cache/selenium

> tree ~/.cache/selenium
/Users/gd/.cache/selenium  [error opening dir]

0 directories, 0 files

When I run this spec Chrome opens, even though I configured my RSpec for Firefox:

> be rspec spec/system/home_spec.rb
.

Finished in 4.49 seconds (files took 2.95 seconds to load)
1 example, 0 failures

At this point selenium-webdriver has reinstalled chromedriver even though I configured my RSpec for geckodriver:

> tree ~/.cache/selenium
/Users/gd/.cache/selenium
├── chromedriver
│   └── mac-arm64
│       └── 119.0.6045.105
│           └── chromedriver
└── se-metadata.json

4 directories, 2 files

How do I get selenium-webdriver to download and use geckodriver instead of chromedriver?

How can we reproduce the issue?

Make a Rails app and configure it to use geckodriver.  Please follow the example above.

Relevant log output

I have no logs, all output is shown above.

Operating System

macOS 14.0

Selenium version

selenium-webdriver 4.15.0

What are the browser(s) and version(s) where you see this issue?

Chrome 119

What are the browser driver(s) and version(s) where you see this issue?

chromedriver 119

Are you using Selenium Grid?

no

[github-actions]

@gdonald, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[github-actions]

Hi, @gdonald.
Please follow the issue template, we need more information to reproduce the issue.

Either a complete code snippet and URL/HTML (if more than one file is needed, provide a GitHub repo and instructions to run the code), the specific versions used, or a more detailed description to help us understand the issue.

Note: If you cannot share your code and URL/HTML, any complete code snippet and URL/HTML that reproduces the issue is good enough.

Reply to this issue when all information is provided, thank you.

[gdonald]

Here's a git repo with a README that describes how to reproduce the issue:

https://github.com/gdonald/selenium-webdriver-bug

[titusfortner]

Your driven_by code is right here:
https://github.com/gdonald/selenium-webdriver-bug/blob/main/test/application_system_test_case.rb#L4

[gdonald]

I'm not running the tests in test. As described in my README, I am running https://github.com/gdonald/selenium-webdriver-bug/blob/main/spec/system/home_spec.rb.

I have deleted the entire tests directory from my repo, and the issue I've described persists.

https://github.com/gdonald/selenium-webdriver-bug

[titusfortner]

Turn on Selenium::WebDriver.logger.level = :debug and it should show where the request for Chrome is coming from.

[titusfortner]

This is why for as much as I like Ruby, I get really frustrated with the Rails approach...

    driven_by(driver)

is calling

RSpec::Rails::SystemExampleGroup#driven_by

which calls from actionpack:

ActionDispatch::SystemTestCase#driven_by

which defaults to:

    def self.driven_by(driver, using: :chrome, screen_size: [1400, 1400], options: {}, &capabilities)
      driver_options = { using: using, screen_size: screen_size, options: options }

      self.driver = SystemTesting::Driver.new(driver, **driver_options, &capabilities)
    end

[gdonald]

Ok, so this using: argument is new to me. When I use that I again have control over which browser I invoke. I've not seen that in any documentation yet, sorry for missing it.

Thanks for the help.

[gdonald]

Turn on Selenium::WebDriver.logger.level = :debug and it
should show where the request for Chrome is coming from.

This works great on Mac and Linux, but not on FreeBSD.

[titusfortner]

Can you turn on logging and provide the output?