Skip to main content

Selenium - OpenQA.Selenium.DriverServiceNotFoundException

With the announcement from Microsoft to stop supporting Coded UI tests, I’m back in Selenium land.

To get it back in my fingers, I started to write a first simple Selenium test:

But although this test looked quite simple, it failed with the following exception:

Test Name:        TestMethod1

Test FullName:  SeleniumTestProject.UnitTest1.TestMethod1

Test Source:       C:\projects\test\SeleniumTestProject\UnitTest1.cs : line 10

Test Outcome:  Failed

Test Duration:   0:00:00,2912324

Result StackTrace:         

at OpenQA.Selenium.DriverService.FindDriverServiceExecutable(String executableName, Uri downloadUrl)

   at OpenQA.Selenium.Chrome.ChromeDriverService.CreateDefaultService()

   at OpenQA.Selenium.Chrome.ChromeDriver..ctor(ChromeOptions options)

   at SeleniumTestProject.UnitTest1.TestMethod1() in C:\projects\test\SeleniumTestProject\UnitTest1.cs:line 15

Result Message:             

Test method SeleniumTestProject.UnitTest1.TestMethod1 threw exception:

OpenQA.Selenium.DriverServiceNotFoundException: The chromedriver.exe file does not exist in the current directory or in a directory on the PATH environment variable. The driver can be downloaded at http://chromedriver.storage.googleapis.com/index.html.

The exception was easy to understand, I needed the chromedriver.exe to spin up a chrome instance. I could follow the suggestions in the exception and download it from http://chromedriver.storage.googleapis.com/index.html. A simpler alternative is adding the Selenium.Chrome.WebDriver NuGet package to your project.

This package does all the work for you: tt installs Chrome Driver(Win32) for Selenium WebDriver into your Unit Test Project and copies the "chromedriver.exe" to the bin folder when building your project.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...