Chris Kenst
The ChromeDriver getting started guide isn’t super helpful if you are unfamiliar with including the ChromeDriver location in your PATH environment variable. (The PATH variable helps Chrome find the downloaded ChromeDriver exe). Also it’s a lot of work for something so common. Never fear, here is a better way:
Installing on macOS:
Listed in order of easiest to hardest install, these are the best ways to install ChromeDriver on a Mac:
- The easiest way to install ChromeDriver is to use your package manager such as brew or npm to install the driver.
- In your terminal window with the Homebrew package manager:
- Install ChromeDriver with brew install cask chromedriver
- Confirm it was installed using chromedriver —version and seeing it returns a version. If it errors it wasn’t installed
- Other package managers like npm have similar commands npm install chromedriver
- In your terminal window with the Homebrew package manager:
- Run Chrome & ChromeDriver in a container using Docker. Simply download the combined container, start it and point your code at the right address.
- Specify it in your Selenium setup code and check it into source control like any other configuration detail. If you go this route, you can include additional drivers like GeckoDriver (aka Firefox) as well.
- Download the driver and add its location to your System PATH.
Which methods have you found the easiest or most success with? Which methods didn’t work for you? Please leave a comment below.
Additional Resources
Oh and if this article worked for you please consider sharing it or buying me coffee to say thanks.
Источник
How to Install Chrome Driver on Mac
Hi, in this tutorial we will learn how to install chrome driver on Mac OS. It is very easy. 😉
Step1: Download Chrome Driver
You need to go to the below address and download the chrome driver for Mac operating system based on (M1 or Intel chip versions).
Download mac64_m1.zip if your mac has Apple Silicon M1 CPU otherwise select the mac64.zip version if your mac has Intel CPU.
Step2: Move the driver to the /usr/local/bin folder
Now, we can move the driver a path which is defined as a path in your system. You can check them with the below command and you will see that /usr/local/bin folder is defined as a global path on your system.
sudo nano /etc/paths
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 chromedriver_mac64.zip file and unpack it. You will see the chromedriver executable file.
Now, we can run the below command and move the chromedriver file to the /usr/local/bin folder.
mv chromedriver /usr/local/bin
And now, you can define chrome driver as shown below in your tests and you can run your selenium tests by using Chrome driver.
If you face “Error: “chromedriver” cannot be opened because the developer cannot be verified. Unable to launch the chrome browser“, you need to go to usr/local/bin folder and right-click chromeDriver file and open it. After this step, re-run your tests, chrome driver will work.
Also, you can use Bonigarcia Webdriver Manager library in your project, for this you need to add its dependency in your project.
Then you can simply use it as follows:
For more complex usage please refer to the webdriver manager GitHub page .
I hope this article helps you and thanks for reading. 🙂 Please feel free to write your comments and questions. 😉
Onur Baskirt is a senior IT professional with 15+ years of experience. Now, he is working as a Senior Technical Consultant at Emirates Airlines in Dubai.
Источник
Downloads
If you are using Chrome version 9 5 , please download ChromeDriver 95.0.4638.17
If you are using Chrome version 9 4 , please download ChromeDriver 94.0.4606.61
If you are using Chrome version 9 3 , please download ChromeDriver 93.0.4577.63
For older version of Chrome, please see below for the version of ChromeDriver that supports it.
If you are using Chrome from Dev or Canary channel, please following instructions on the ChromeDriver Canary page.
For more information on selecting the right version of ChromeDriver, please see the Version Selection page.
Supports Chrome version 95
Resolved issue 3857: Host header or origin header is specified and is not whitelisted or localhost [Pri-1]
Added ` —allowed-origins ` argument
For more details, please see the release notes .
Supports Chrome version 9 5
Resolved issue 3857: Host header or origin header is specified and is not whitelisted or localhost [Pri-1]
Added ` —allowed-origins ` argument
For more details, please see the release notes .
Supports Chrome version 94
For more details, please see the release notes .
Supports Chrome version 9 4
For more details, please see the release notes .
Supports Chrome version 93
For more details, please see the release notes .
Supports Chrome version 9 3
For more details, please see the release notes .
Supports Chrome version 92
For more details, please see the release notes .
Supports Chrome version 9 2
Resolved issue 3389: Host validation for ChromeDriver requests
For more details, please see the release notes .
Supports Chrome version 91
Resolved issue 1205107 : Unable to get attribute value for fields on the web application.
For more details, please see the release notes .
Supports Chrome version 91
Resolved issue 3744: SendKeys() and Click() silently fail after link navigation
Resolved issue 3746: attribute endpoint incorrectly updates values
For more details, please see the release notes .
Supports Chrome version 90
Resolved issue 3708: GetElementLocation’s inView fails for elements in shadow DOM
Resolved issue 3721: Collect performance log for service worker when enabled
Resolved issue 3731: AdbImpl::GetPidByName does not work correctly on non-standard Android OS’s like on OnePlus
Resolved issue 3733: Catastrophic failure with domain on localhost
Resolved issue 3734: Driver should Error Attempting to set Cookie on Wrong Domain
Resolved issue 3743: Refactor call function and fix remove element issue
For more details, please see the release notes .
Supports Chrome version 89
Resolved issue 3667: Timed out receiving a message from renderer
Resolved issue 3675: GetElementLocation uses inView method which mishandles boolean as array
Resolved issue 3682: GetElementRegion returns incorrect size for elements which are partially out of viewport
Resolved issue 3690: ChromeDriver fails if extensions use chrome.windows API
For more details, please see the release notes .
Supports Chrome version 88
Resolved issue 3641: Page not getting loaded/rendered when browser window is not in focus with Chrome Beta v87 and chromedriver v(87/86)
For more details, please see the release notes .
Supports Chrome version 88
Resolved issue 3611: getText() output in protractor different from .innerText
Resolved issue 3625: Improve element screenshot compatibility
Resolved issue 3628: Stale Element Reference and wrong URL reported back with URL having another URL as part of its path
Resolved issue 3631: Add support for the `webauthn:extension:largeBlob` capability
Resolved issue 3635: Chromedriver 86 — chromedriver .quit() doesn’t seem to pass unload event properly
Resolved issue 3649: Copying selected text to clipboard does not work on Windows 10 when using headless mode
For more details, please see the release notes .
Supports Chrome version 87
Resolved issue 3641: Page not getting loaded/rendered when browser window is not in focus with Chrome Beta v87 and chromedriver v(87/86)
Resolved issue 3657: Screenshot background browser timed out
For more details, please see the release notes .
Supports Chrome version 87
Resolved issue 2421: Delete old port-forwarding channels on android adb-server
Resolved issue 3474: Emulated mobile device list needs updating
Resolved issue 3507: Implement «get computed role»
Resolved issue 3508: Implement «get computed label»
Resolved issue 3584: Rename ChromeDriver command line option —whitelisted-ips
Resolved issue 3588: Bidi WebSocket connection
Resolved issue 3594: Navigation completes prematurely if OOPIF loads before main page
Resolved issue 3598: A command line option for devtools port to be forwarded to webview_devtools_remote socket
Resolved issue 3608: Chromedriver debuggerAddress does not support ipv6
For more details, please see the release notes .
Supports Chrome version 86
Resolved issue 3370: Shut down Chrome gracefully or cookie will not be correctly saved to SQLite persistence file
Resolved issue 3401: Get Element Location JS does not locate the visible center of the element
Resolved issue 3462: For sendKeys, CMD key don’t work for MAC
Resolved issue 3541: Improve log between Client and ChromeDriver
Resolved issue 3559: Output Chrome version when ChromeDriver reports incompatible
For more details, please see the release notes .
Supports Chrome version 85
Resolved issue 3578: Chrome 85 no longer allows graceful interaction with windows when an alert dialog is open
For more details, please see the release notes .
Supports Chrome version 85
Resolved issue 3577: ChromeDriver 85 does not detect changed Chrome directory (C:\Program Files)
For more details, please see the release notes .
Supports Chrome version 85
Resolved issue 3214: ChromeDriver78: Sendkeys resets text selection with contenteditable
Resolved issue 3376: Remove LaunchApp command from ChromeDriver
Resolved issue 3432: Sometimes NavigationTracker fails to detect when the page has finished loading
Resolved issue 3481: New Print endpoint according to w3c spec
Resolved issue 3488: driver.get doesn’t throw error when proxy is wrong configured
Resolved issue 3502: Use document.hasFocus() to check if element is focused
Resolved issue 3515: selenium.common.exceptions.WebDriverException: Message: unknown error: bad inspector message
For more details, please see the release notes .
Источник
Using Selenium Chrome Driver on Mac OS X
Update (26/06/2015)
Previously I have written a function which waits until a specific element is available on the page, doWhenAvailable. I have find out Selenium has already a similar feature build-in. Its element search functions could wait until an element is available on the page. It can be activated in @BeforeClass method:
[code language=”java”]driver. manage( .timeouts( ). implicitlyWait(TIMEOUT_TIME, TimeUnit.SECONDS) ;
[/code]
[code language=”java”]//doWhenAvailable(driver, By.id( “view_profile”), WebElement::click);
driver.findElement(By.id(“view_profile”)).click() ;[/code]
It took several attempts for me able to use Chrome Driver by using the instructions from its website and I have decided to publish a step by step tutorial.
Selenium allows you to run your tests using several different browsers Chrome, Firefox, InternetExplorer and HTMLUnit. HTMLUnit is not a real browser it is just a browser simulator written in Java, it can execute JavaScript too. Some settings you have to use for each one is different but for all of them you have to start by adding main Selenium dependency to you project. This is the common part.
Creating Maven Project
I have created a new maven project using following pom.xml but you can just add selenium dependency to your own pom.xml if you want. Here is the pom.xml file I have used for my test project:
WebDriver Specific Initialization
For newcomers it is best to stick with Firefox. It is easier to setup. After installing Firefox browser to you system just create a new FirefoxDriver and start running your project. There are no extra step required.
For Chrome in addition to Chrome Browser you have to install Chrome Driver too. You can download Chrome Driver from Chromium web site and put it in a suitable place in your system. Location is not important because we will be providing location of it through a system property to our test execution.
In my case I have put chromedriver executable to Applications folder. So for my JUnit test I have use following setting:
[code language=”java”]System.setProperty(«webdriver.chrome.driver» , «/Applications/chromedriver»);
[/code]
Writing Actual Test Codes
We have to initialize our WebDriver instance, since I am using JUnit I have done it in @BeforeClass so it is automatically run before my test cases. You can also do this before every test case using @BeforeTest but it will be a lot slower because you will most probably do extra initialization than shown below. For example logging-in to web site.
[code language=”java”]
@BeforeClass
public static void init() <
driver = new ChromeDriver(); //init chrome driver
//driver = new FirefoxDriver(); //uncomment to use Firefox
driver.get(«http://localhost:8080”); //url of website we like to test
driver.manage().window().setSize(new Dimension(1600, 900)); //resize browser window
//login to web site
>
[/code]
You will most probably want browser to automatically closed after your tests are completed. Add driver.quit() to your JUnit teardown method. If you do not each execution will left a new browser window open.
[code language=”java”]@AfterClass
public static void teardown() <
driver.quit();
>
[/code]
Nowadays nearly all web applications will be loaded asynchronously. That mean when page is loaded the element you like to test will not be on the page, it will be generated by a JavaScript code. This makes writing test a little more difficult, you have to wait until related element is created by JavaScript code. I have writing a small helper function and reused it in my test code. It waits until given element (Specified using By) is available on the page and execute the given code block (Consumer) when the element is available:
[code language=”java”]public static void doWhenAvailable( WebDriver driver , By by , Consumer consumer ) <
( new WebDriverWait (driver, TIMEOUT_TIME ) ).until( ( WebDriver drv ) -> driver.findElement( by ) != null ) ;
consumer.accept( driver.findElement( by ) ) ;
>[/code]
Using this method with Java 8 is very readable. For example below code waits until an element with id=“view_profile” is available on the page and when it is available just clicks on it.
[code language=”java”]
doWhenAvailable(driver, By.id(«view_profile»), WebElement::click);
[/code]
Following code performs more complex operation when requested element is available. It wails until select element is available on the page and select option element which has a value of “Jan”:
[code language=”java”]
doWhenAvailable(driver, By.id(«ts_month_picker_selector»), (element) -> <
Select select = new Select(element);
select.selectByValue(String.valueOf(“Jan»));
>);
[/code]
You will mostly need to perform other asynchronous operations inside the callback and this will result into callback hell. I am still looking a way to promise style of chaining asynchronous operations.
Источник
