NuGet package - Selenium WebDriver ChromeDriver

NuGet Package NuGet Package NuGet Package

What'due south this?

This NuGet package installs Chrome Driver (Win32, macOS, and Linux64) for Selenium WebDriver into your Unit of measurement Test Projection.

"chromedriver(.exe)" does non appear in Solution Explorer, just it is copied to the output binder from the bundle source folder when the build process.

NuGet bundle restoring gear up, and no demand to commit "chromedriver(.exe)" binary into source code control repository.

How to install?

For case, at the package manager console on Visual Studio, enter the following command.

If you are using Chrome version 99:

              PM> Install-Parcel Selenium.WebDriver.ChromeDriver -Version 99.0.4844.5100                          

If you are using Chrome version 98:

              PM> Install-Package Selenium.WebDriver.ChromeDriver -Version 98.0.4758.10200                          

If you are using Chrome version 97:

              PM> Install-Packet Selenium.WebDriver.ChromeDriver -Version 97.0.4692.7100                          

To larn what version of ChromeDriver you lot demand to use, please come across as well the post-obit page:

https://chromedriver.chromium.org/downloads/version-selection

Cross-platform building and publishing

By default - information technology depends on the Os running the build process

Past default, the platform blazon of the spider web driver file copied to the output binder depends on the OS running the build procedure.

  • When you lot build the project which references the NuGet package of chromedriver on Windows Bone, win32 version of chromedriver will exist copied to the output binder.
  • When you build it on macOS, macOS x64 version of chromedriver will be copied to the output folder.
  • When you build information technology on any Linux distributions, Linux x64 version of chromedriver volition exist copied to the output folder.

Method 1 - Specify "Runtime Identifier"

When you specify the "Runtime Identifier (RID)" explicitly, the platform type of the driver file is the same to the RID which y'all specified. (it doesn't depends on the which Bone to use for build process.)

You can specify RID every bit a MSBuild belongings in a projection file,

              <PropertyGroup>   <RuntimeIdentifier>win-x64</RuntimeIdentifier> </PropertyGroup>                          

or, as a control-line -r pick for dotnet build control.

              > dotnet build -r:osx.10.12-x64                          
  • When the RID that starts with "win" is specified, win32 version of chromedriver volition be copied to the output folder.
  • When the RID that starts with "osx" is specified, macOS x64 version of chromedriver volition be copied to the output binder.
  • When the RID that starts with "linux" is specified, Linux x64 version of chromedriver will be copied to the output folder.

If you specify another pattern of RID like "ubuntu.xviii.04-x64", the platform blazon of the web driver file which will be copied to the output folder depends on the Os running the build process. (default behavior.)

Method two - Specify "WebDriverPlatform" msbuild property

Y'all can control which platform version of chromedriver will be copied by specifying "WebDriverPlatform" MSBuild property.

"WebDriverPlatform" MSBuild property can take 1 of the post-obit values:

  • "win32"
  • "mac64"
  • "linux64"

You can specify "WebDriverPlatform" MSBuild property in a project file,

              <PropertyGroup>   <WebDriverPlatform>win32</WebDriverPlatform> </PropertyGroup>                          

or, command-line -p pick for dotnet build control.

              > dotnet build -p:WebDriverPlatform=mac64                          

The specifying "WebDriverPlatform" MSBuild belongings is the highest priority method to control which platform version of the chromedriver will be copied.

If yous run the post-obit command on Windows OS,

              > dotnet build -r:ubuntu.18.04-x64 -p:WebDriverPlatform=mac64                          

The driver file of macOS x64 version will be copied to the output binder.

How to include the commuter file into published files?

"chromedriver(.exe)" isn't included in published files on default configuration. This behavior is by design.

If you desire to include "chromedriver(.exe)" into published files, please ascertain _PUBLISH_CHROMEDRIVER compilation symbol.

define _PUBLISH_CHROMEDRIVER compilation symbol

Another mode, you can define PublishChromeDriver belongings with value is "true" in MSBuild file (.csproj, .vbproj, etc...) to publish the commuter file instead of define compilation symbol.

                              <Projection ...>     ...     <PropertyGroup>       ...       <PublishChromeDriver>truthful</PublishChromeDriver>       ...     </PropertyGroup> ... </Project>                          

You can likewise ascertain PublishChromeDriver property from the command line -p option for dotnet publish command.

              > dotnet publish -p:PublishChromeDriver=true                          
Note

PublishChromeDriver MSBuild property e'er override the status of define _PUBLISH_CHROMEDRIVER compilation symbol or not. If you define PublishChromeDriver MSBuild property with faux, then the driver file isn't included in publish files whenever define _PUBLISH_CHROMEDRIVER compilation symbol or not.

Appendix

The numbering of the package version

The rule of the version number of this package is:

chromedriver version MAJOR.MINOR.BUILD.PATCH + package version (2 digit)

For example, 2nd packet release for the chromedriver ver.i.2.3.4, the packet version is ane.2.3.4 + 021.ii.iii.402.

Sometime multiple packages for the same chromedriver version may be released by following instance reasons.

  • Packaging miss. (the package included invalid version of the driver files)
  • Fixing problems of the build script, or improving the build script.

Where is chromedriver.exe saved to?

chromedriver(.exe) exists at
" {solution folder} /packages/Selenium.WebDriver.ChromeDriver. {ver} /driver/ {platform}"
folder.

                              {Solution folder}/   +-- packages/   |   +-- Selenium.WebDriver.ChromeDriver.{version}/   |       +-- commuter/   |       |   +-- win32   |       |       +-- chromedriver.exe   |       |   +-- mac64   |       |       +-- chromedriver   |       |   +-- linux64   |       |       +-- chromedriver   |       +-- build/   +-- {projection folder}/       +-- bin/           +-- Debug/           |   +-- chromedriver(.exe) (copy from in a higher place by build procedure)           +-- Release/               +-- chromedriver(.exe) (copy from above past build procedure)                          

And package installer configure MSBuild task such as .csproj to copy chromedriver(.exe) into the output folder during the build process.

License

The build script (.targets file) in this NuGet package is licensed under The Unlicense.

The binary files of ChromeDriver are licensed nether the BSD-3-Clause.

This package has no dependencies.

NuGet packages (112)

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

Package Downloads
Pangolin

A framework for declarative UI testing for ASP.NET apps. Browsers: Chrome (>=96) Firefox (>=70) IE (>=11) Dependencies: MSharp Projection: MSharp.Framework (>= iv.0.110) Olive Project: Olive.Testing (>= 2.1.113)

SpecsFor.Mvc

SpecsFor.Mvc is a stand up-alone acceptance testing framework for ASP.NET MVC. Information technology enables you to write strongly-typed, refactor friendly integration tests using the browser and testing framework of your pick.

Objectivity.Examination.Automation.Common.NUnit

[DEPRECATED] Apply Install-Package Ocaramba.Features Install-Bundle Ocaramba.MsTest Install-Bundle Ocaramba.NUnit Install-Parcel Ocaramba.xUnit instead

Selenium.Helper

This bundle contains .NET helper classes to make the cosmos of Selenium tests easier. It contains a Connector class that supports various initializations of the Commuter. It likewise contains a utility class to assist in working with elements.

Ocaramba

Framework to automate tests using Selenium WebDriver

GitHub repositories (36)

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

Repository Stars
Radarr/Radarr

A fork of Sonarr to piece of work with movies à la Couchpotato.

btcpayserver/btcpayserver

Accept Bitcoin payments. Free, open-source & cocky-hosted, Bitcoin payment processor.

aspnet/KestrelHttpServer

[Archived] A cross platform spider web server for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore

mono/SkiaSharp

SkiaSharp is a cantankerous-platform second graphics API for .Cyberspace platforms based on Google'south Skia Graphics Library. Information technology provides a comprehensive 2D API that can be used across mobile, server and desktop models to render images.

Lidarr/Lidarr

Looks and smells like Sonarr merely fabricated for music.

Version Downloads Last updated
100.0.4896.2000-beta 697 3/four/2022
99.0.4844.5100 40,036 three/four/2022
99.0.4844.5100-beta 1,117 3/ii/2022
99.0.4844.3500-beta 986 2/17/2022
99.0.4844.1700-beta 941 2/5/2022
98.0.4758.10200 99,538 2/15/2022
98.0.4758.8000 156,991 2/4/2022
98.0.4758.4800 31,148 2/3/2022
98.0.4758.4800-beta 20,403 1/12/2022
97.0.4692.7100 323,930 i/half dozen/2022
97.0.4692.3600-beta vi,852 12/3/2021
97.0.4692.2000-beta 5,452 xi/xix/2021
96.0.4664.4500 700,397 11/sixteen/2021
96.0.4664.3500-beta three,281 eleven/8/2021
96.0.4664.1800-beta.two 443 11/3/2021
96.0.4664.1800-beta two,012 10/25/2021
95.0.4638.6900 138,136 xi/8/2021
95.0.4638.5401 78,408 11/three/2021
95.0.4638.5400 84,804 10/28/2021
95.0.4638.1700 176,538 x/20/2021
95.0.4638.1700-beta ten,723 9/28/2021
95.0.4638.m-beta i,790 nine/21/2021
94.0.4606.11300 5,551 11/8/2021
94.0.4606.6100 433,553 ix/28/2021
94.0.4606.4101 131,695 9/22/2021
94.0.4606.4101-beta 2,441 ix/x/2021
93.0.4577.6300 120,610 9/14/2021
93.0.4577.1500 254,489 9/1/2021
93.0.4577.1500-beta 8,833 seven/29/2021
92.0.4515.10700 498,723 7/29/2021
92.0.4515.4300 182,978 7/21/2021
92.0.4515.4300-beta 5,196 6/12/2021
91.0.4472.10100 464,575 6/12/2021
91.0.4472.1900 415,083 5/26/2021
91.0.4472.1900-beta 4,789 4/23/2021
ninety.0.4430.2400 802,058 4/14/2021
ninety.0.4430.2400-beta 5,972 three/sixteen/2021
89.0.4389.2300 846,548 three/4/2021
89.0.4389.2300-beta 7,473 1/29/2021
88.0.4324.9600 706,965 i/21/2021
88.0.4324.2700 44,369 i/19/2021
88.0.4324.2700-beta iii,471 12/4/2020
87.0.4280.8800 1,055,030 12/ii/2020
87.0.4280.2000 377,972 11/18/2020
87.0.4280.2000-beta 26,794 10/17/2020
86.0.4240.2200 609,909 10/9/2020
86.0.4240.2200-beta 15,233 nine/4/2020
85.0.4183.8700 888,406 8/28/2020
85.0.4183.8300 169,172 8/26/2020
85.0.4183.3800-beta 5,060 seven/24/2020
84.0.4147.3001 383,656 vii/15/2020
84.0.4147.3001-beta 647 vii/12/2020
84.0.4147.3000-beta 7,584 5/29/2020
83.0.4103.3915 34,232 7/15/2020
83.0.4103.3915-beta 1,946 7/11/2020
83.0.4103.3910 186,857 vi/28/2020
83.0.4103.3910-beta 8,197 five/24/2020
83.0.4103.3900 903,894 five/20/2020
83.0.4103.3900-beta xvi,388 5/6/2020
83.0.4103.1400-beta 5,446 four/17/2020
81.0.4044.13800 130,862 5/6/2020
81.0.4044.6900 303,680 4/nine/2020
81.0.4044.6900-beta ii,007 3/eighteen/2020
81.0.4044.2000-beta 3,787 two/14/2020
80.0.3987.10600 807,165 2/14/2020
80.0.3987.1600 255,648 2/5/2020
80.0.3987.1600-beta iii,129 12/20/2019
79.0.3945.3600 796,768 12/12/2019
79.0.3945.3600-beta 17,858 xi/19/2019
79.0.3945.1600-beta one,653 10/31/2019
78.0.3904.10500 298,232 xi/19/2019
78.0.3904.7000 454,814 ten/23/2019
78.0.3904.1100-beta three,979 ix/xiii/2019
77.0.3865.4000 457,624 ix/13/2019
77.0.3865.4000-beta ii,500 8/21/2019
77.0.3865.ten-beta 5,846 8/7/2019
76.0.3809.12600 243,178 8/22/2019
76.0.3809.6801 94,836 8/12/2019
76.0.3809.68 148,937 8/5/2019
76.0.3809.68-beta iv,945 7/17/2019
76.0.3809.25-beta 3,541 half-dozen/14/2019
76.0.3809.12-beta 726 vi/8/2019
75.0.3770.140 277,557 7/14/2019
75.0.3770.90 204,549 half dozen/14/2019
75.0.3770.eight 59,365 6/viii/2019
74.0.3729.6 439,611 four/25/2019
73.0.3683.68 270,556 three/13/2019
72.0.3626.69 379,923 3/five/2019
71.0.3578.137 38,435 3/5/2019
2.46.0 346,200 2/2/2019
2.45.0 348,824 12/11/2018
ii.44.0 326,438 11/21/2018
2.43.0 831,317 10/18/2018
2.42.0.1 359,901 9/14/2018
two.41.0 519,687 7/28/2018
2.40.0 733,417 6/8/2018
2.39.0 92,100 five/30/2018
two.38.0.1 410,472 iv/26/2018
2.38.0 420,948 4/xviii/2018
2.37.0 585,799 3/17/2018
2.36.0 240,995 iii/2/2018
2.35.0 438,064 1/11/2018
2.34.0 123,624 12/10/2017
2.33.0 453,509 10/4/2017
2.32.0 148,268 eight/31/2017
two.31.0 122,076 7/23/2017
2.30.0.one 415,563 6/8/2017
2.29.0 340,777 four/4/2017
2.28.0.2-beta 1,967 3/21/2017
2.28.0.i-beta 3,104 iii/nine/2017
2.28.0 112,046 3/nine/2017
two.27.0.seven-beta 2,233 3/3/2017
2.27.0.half dozen-beta 743 3/two/2017
2.27.0.2-beta 959 2/28/2017
2.27.0 248,432 12/22/2016
2.26.0 55,501 12/vi/2016
ii.25.0.8 114,577 11/xv/2016
two.25.0.viii-beta 4,973 10/29/2016
two.25.0 93,978 x/24/2016
2.24.0 128,065 9/16/2016
2.23.0.1 100,457 8/x/2016
two.23.0 3,892 8/9/2016
ii.22.0 97,884 vi/eight/2016
2.21.0.1-beta 2,562 five/5/2016
2.21.0 199,172 1/26/2016
2.20.0 156,545 x/9/2015
2.19.0 42,675 ix/6/2015
2.18.0 10,357 eight/22/2015
two.17.0 eight,130 eight/12/2015
ii.16.0 15,822 6/27/2015
two.15.0 39,220 4/1/2015
ii.fourteen.0.1-beta 984 3/vi/2015
ii.14.0 18,482 3/3/2015
2.13.0 17,681 1/six/2015
ii.12.0 xviii,524 10/30/2014
ii.ten.0.i-beta2 i,889 8/14/2014
2.ten.0.one-beta 799 8/14/2014
2.x.0 27,880 v/eight/2014
2.ix.0.ane five,661 four/7/2014
2.ix.0.i-beta3 924 4/5/2014
2.9.0.one-beta2 911 four/3/2014
2.9.0 9,349 3/27/2014
2.8.0 10,077 1/24/2014
2.3.0 viii,088 9/7/2013
ii.ii.0 6,255 8/28/2013

99.0.4844.5100
- Chrome Commuter 99.0.4844.51 release