Once you’ve obtained a client library, you can write a WebDriver test and run it against Safari. The example below uses using Python WebDriver to test important functionality of the WebKit Feature Status page. In the Python WebDriver library, each method call synchronously blocks processes until the operation completes. If you want you can add a specific path here and you can move the chromedriver to this folder but as you see, /usr/local/bin folder is defined as a path by default. Now, go to your downloads folder, find the chromedrivermac64.zip file and unpack it. WebDriver can drive Firefox without the need of a driver server Starting Firefox 45 & above one needs to use gecko driver created by Mozilla for automation: Internet Explorer: Internet Explorer Driver Server: Available in 32 and 64-bit versions. Use the version that corresponds to the architecture of your IE: Chrome: ChromeDriver. Each version of ChromeDriver supports Chrome with matching major, minor, and build version numbers. For example, ChromeDriver 73.0.3683.20 supports all Chrome versions that start with 73.0.3683. Before a new major version of Chrome goes to Beta, a matching version of ChromeDriver will be released.

Repurposed nuget package of Selenium.WebDriver.ChromeDriver (packing process differs slightly)
Install Chrome Driver(Win32) for Selenium WebDriver into your Unit Test Project.
'chromedriver.exe' is copied to bin folder from package folder when the build process.
NuGet package restoring ready, and no need to commit 'chromedriver.exe' binary into source code control repository.

NuGet packages for WebDriver - Chrome, Firefox, Internet Explorer, PhantomJS

This is a repurposed repo of nupkg-selenium-webdriver-chromedriver by jsakamoto that handles downloading Chrome, Firefox, Internet Explorer WebDrivers, and PhantomJS instead

Chrome:

Firefox:

InternetExplorer:

PhantomJS:

These NuGet packages will download Selenium WebDrivers (Chrome, Firefox, Internet Explorer, and PhantomJS) into your Unit Test Project.
Each WebDriver binary file does not appear in Solution Explorer, but it is copied to bin folder from package folder when the build process.
NuGet package restoring ready, and no need to commit any WebDriver binary files into source code control repository.

How to install?

For example, at the package manager console on Visual Studio, enter following command to install ChromeDriver

For Firefox WebDriver (Marionette)

For Internet Explorer Driver 32bit

For PhantomJS (Windows)

Detail

Where is each WebDriver binary file saved to?

Each WebDriver will be downloaded to their respective nuget package location:

{solution folder}/packages/Selenium.{browser}.WebDriver. {ver} /driver

And package installer configure msbuild task such as .csproj to copy each WebDriver binary file into output folder during build process.

How to build each nuget package?

You will need to execute the BuildPackage.bat file with the following input parameters:

• Browser {Chrome, Firefox, IE, PhantomJS}
• Version
• (OPTIONAL) Binary File Bit Version 32 or 64 (defaults to 32bit)

Usage Examples

BuildPackage.bat {browser} {version} {OPTIONAL|bitversion}

For creating nuget package for ChromeDriver version 2.25:

For creating nuget package for Firefox (Marionette) Driver version 0.11.1:

For creating nuget package for Internet Explorer Driver version 2.48:

For creating nuget package for Internet Explorer Driver version 3.8.0 64bit version:

For creating nuget package for PhantomJS version 2.1.1:

NuGet packages for WebDriver - Chrome, Firefox, Internet Explorer, PhantomJS

This is a repurposed repo of nupkg-selenium-webdriver-chromedriver by jsakamoto that handles downloading Chrome, Firefox, Internet Explorer WebDrivers, and PhantomJS instead

Chrome:

Firefox:

InternetExplorer:

Chromedriver Webdriver For Chrome

PhantomJS:

These NuGet packages will download Selenium WebDrivers (Chrome, Firefox, Internet Explorer, and PhantomJS) into your Unit Test Project.
Each WebDriver binary file does not appear in Solution Explorer, but it is copied to bin folder from package folder when the build process.
NuGet package restoring ready, and no need to commit any WebDriver binary files into source code control repository.

How to install?

For example, at the package manager console on Visual Studio, enter following command to install ChromeDriver

For Firefox WebDriver (Marionette)

For Internet Explorer Driver 32bit

For PhantomJS (Windows)

Detail

Where is each WebDriver binary file saved to?

Each WebDriver will be downloaded to their respective nuget package location:

{solution folder}/packages/Selenium.{browser}.WebDriver. {ver} /driver

And package installer configure msbuild task such as .csproj to copy each WebDriver binary file into output folder during build process.

How to build each nuget package?

You will need to execute the BuildPackage.bat file with the following input parameters:

• Browser {Chrome, Firefox, IE, PhantomJS}
• Version
• (OPTIONAL) Binary File Bit Version 32 or 64 (defaults to 32bit)

Usage Examples

BuildPackage.bat {browser} {version} {OPTIONAL|bitversion}

For creating nuget package for ChromeDriver version 2.25:

For creating nuget package for Firefox (Marionette) Driver version 0.11.1:

For creating nuget package for Internet Explorer Driver version 2.48:

For creating nuget package for Internet Explorer Driver version 3.8.0 64bit version:

For creating nuget package for PhantomJS version 2.1.1:

Release Notes

v2.39 - Chrome Driver 2.39 release - https://chromedriver.storage.googleapis.com/index.html?path=2.39/
v2.38 - Chrome Driver 2.38 release - https://chromedriver.storage.googleapis.com/index.html?path=2.38/
v2.37 - Chrome Driver 2.37 release - https://chromedriver.storage.googleapis.com/index.html?path=2.37/
v2.36 - Chrome Driver 2.36 release - https://chromedriver.storage.googleapis.com/index.html?path=2.36/
v2.35 - Chrome Driver 2.35 release - https://chromedriver.storage.googleapis.com/index.html?path=2.35/
v2.34 - Chrome Driver 2.34 release - https://chromedriver.storage.googleapis.com/index.html?path=2.34/
v2.33 - Chrome Driver 2.33 release - https://chromedriver.storage.googleapis.com/index.html?path=2.33/
v2.32 - Chrome Driver 2.32 release - https://chromedriver.storage.googleapis.com/index.html?path=2.32/
v2.31 - Chrome Driver 2.31 release - https://chromedriver.storage.googleapis.com/index.html?path=2.31/
v2.30 - Chrome Driver 2.30 release - https://chromedriver.storage.googleapis.com/index.html?path=2.30/
v2.29 - Chrome Driver 2.29 release - https://chromedriver.storage.googleapis.com/index.html?path=2.29/
v2.28 - Chrome Driver 2.28 release - https://chromedriver.storage.googleapis.com/index.html?path=2.28/
v2.27 - Chrome Driver 2.27 release - https://chromedriver.storage.googleapis.com/index.html?path=2.27/
v2.26 - Chrome Driver 2.26 release - https://chromedriver.storage.googleapis.com/index.html?path=2.26/
v2.25.0.1 - Fixed package so it now includes the correct Web Driver (i.e. Chrome Driver 2.25)
v2.25 - Chrome Driver 2.25 release - https://chromedriver.storage.googleapis.com/index.html?path=2.25/

Dependencies

This package has no dependencies.

Used By

NuGet packages (48)

Chrome Webdriver Download

Showing the top 5 NuGet packages that depend on Selenium.Chrome.WebDriver:

GitHub repositories (8)

Showing the top 5 popular GitHub repositories that depend on Selenium.Chrome.WebDriver:

Version History