selenium-ide: [🐛 Bug]: Unable to obtain browser driver

What happened?

Unable to get side runner working on any new machine or -reinstalled- machine where side runner was working on before reinstallation.

How can we reproduce the issue?

Fresh install of Windows 11 (x64) (or spin up a new  x64 VM)
Download (and install) Firefox ("Firefox Setup 121.0.1.exe" | x64)
Download (and install) NodeJS (node-v20.11.0-x64.msi)

==reboot==

Start cmd. All below commands are entered in the user dir

npm install -g selenium-side-runner
npm install -g geckodriver
selenium-side-runner --version >>>>>> 4.0.0-alpha.63
geckodriver --version >>>>>> driver file is being downloaded to directory: %USERPROFILE%\AppData\Local\Temp

close cmd
Add %USERPROFILE%\AppData\Local\Temp to PATH user variable

== reboot (and check if new PATH location is present with echo %PATH%) ==

start cmd
selenium-side-runner -c "browserName=firefox" Desktop\test.side

Result: "Unable to obtain browser driver."

Relevant log output

C:\Users\QQQ>selenium-side-runner -c "browserName=firefox" Desktop\test.side
info: Running test test
info: Building driver for firefox
 FAIL  AppData/Roaming/npm/node_modules/selenium-side-runner/dist/main.test.js
  Running project test
    Running suite Default Suite
      × Running test test (49 ms)

  ● Running project test › Running suite Default Suite › Running test test

    Unable to obtain browser driver.
            For more information on how to install drivers see
            https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location/. Error: Error executing command for C:\Users\QQQ\AppData\Roaming\npm\node_modules\selenium-side-runner\node_modules\selenium-webdriver\bin\windows\selenium-manager.exe with --browser,firefox,--output,json: undefined

      at getPath (node_modules/selenium-webdriver/common/driverFinder.js:35:11)
      at Function.createSession (node_modules/selenium-webdriver/firefox.js:603:45)
      at createDriver (node_modules/selenium-webdriver/index.js:152:33)
      at Builder.build (node_modules/selenium-webdriver/index.js:688:16)
      at WebDriverExecutor.init (node_modules/@seleniumhq/side-runtime/src/webdriver.ts:170:10)
      at Playback.init (node_modules/@seleniumhq/side-runtime/src/playback.ts:140:25)
      at Playback.play (node_modules/@seleniumhq/side-runtime/src/playback.ts:162:46)
      at src/run.ts:157:11

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        2.099 s, estimated 11 s
Ran all test suites within paths "C:\Users\QQQ\AppData\Roaming\npm\node_modules\selenium-side-runner\dist\main.test.js".

C:\Users\QQQ>

Operating System

Windows 11 Pro (up-to-date)

Selenium version

selenium-side-runner: 4.0.0-alpha.63. .side file is created with IDE (firefox) plugin

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

all (in example above Firtefox 121.0.1 was used)

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

geckodriver 0.34.0

Are you using Selenium Grid?

no

About this issue

  • Original URL
  • State: open
  • Created 5 months ago
  • Comments: 30 (14 by maintainers)

Most upvoted comments

@toddtarsi & @GT-VMC876 Just for the record… I am able to run my test code (.side) using selenium-side-runner (4.0.0-alpha.66) with Chrome (version 121.0.6167.161).

Okay, so this happens, and a question that commonly arises for me is like “how can i tell where the problem is coming from in this ecosystem”. I think I need to add a command to selenium-side-runner to debug this sort of thing. Let me add a command onto selenium-side-runner focused on debugging ability to connect to a driver instance or something.