Test will freeze/fail, trying to download driver binary, when developer computer is temporarily offline

[bonigarcia]

Test will freeze/fail, trying to download driver binary, when developer computer is temporarily offline

[bonigarcia]

Use a fixed version of chromedriver instead of reading to the repository to get the latest version. That should do the trick. For example:

ChromeDriverManager.getInstance().setup("2.21");

[djangofan]

Using your suggestion didn't change anything about the behavior:
ChromeDriverManager.getInstance().setup("2.21");
So, I have this setup in my application.properties :

wdm.chromeDriverUrl=http://chromedriver.storage.googleapis.com/
wdm.chromeDriverExport=webdriver.chrome.driver
wdm.chromeDriverVersion=2.21

And I start the driver like this:
ChromeDriverManager.getInstance().setup(Architecture.x32);
So, my question is: WHY would you suggest I call setup with a version number if I clearly state the version number that I want in my application.properties file? Also, if I want to run a previously download driver: 2.18, 2.20, or whatever, why does your code ALWAYS try to download via the wdm.chromeDriverUrl when the driver (with that version) was already previously download by WDM?

[bonigarcia]

There was an issue related to this in version 1.4.1. Test with WebDriverManager 1.4.2 and the following command:

ChromeDriverManager.getInstance().setup(Architecture.x32, "2.21");

[djangofan]

It works now for me, thanks. Forgot to tell you that I think.

[djangofan]

Was having this problem again on version 1.4.1 and I just verified again that version 1.4.2 fixes the problem. Thanks again.

[andrey-epifanov]

hello !
Many thanks for your library ! :)
I have such case.
And this fix is available for versions of chrome driver like 2.0 - 2.24 .
But http://chromedriver.storage.googleapis.com does not contain 3.0.1 chromedriver , that's why it is not work with 3.0.1 .
Can it be fixed?

Andrey

[bonigarcia]

@andrey-epifanov I don't understand your point. The latest version of chromedriver at writing time is 2.27. You should be able to use ChromeDriverManager to force a given version, for example this way:

ChromeDriverManager.getInstance().setup("2.27");

What's the problem?

[djangofan]

He is right, that site only hosts ChromeDriver up to version 2.27 : https://sites.google.com/a/chromium.org/chromedriver/home As far as I can tell, there is not a ChromeDriver version higher than 2.27: SeleniumHQ/selenium#2566

…

On Tue, Jan 24, 2017 at 7:10 AM, Boni García ***@***.***> wrote: @andrey-epifanov <https://github.com/andrey-epifanov> I don't understand your point. The latest version of *chromedriver* at writing time is 2.27. You should be able to use ChromeDriverManager to force a given version, for example this way: ChromeDriverManager.getInstance().setup("2.27"); What's the problem? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#24 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAxfjmgnqOup0X4epg-kpNVg106_vhiAks5rVhR4gaJpZM4H63jm> .

[andrey-epifanov]

Official Selenium News
http://www.seleniumhq.org/about/news.jsp

Also I try to research pages / sites like http://chromedriver.storage.googleapis.com with higher version of ChromeDriver , and don't find.

[bonigarcia]

You are confusing the version of Selenium WebDriver which is 3.x with the version of chromedriver, which is the specific binary aimed to control Google Chrome browser with Selenium Webdriver. The latest version of chromedriver, as I said before is 2.27 currently.

[andrey-epifanov]

May be. Sorry if I have mistake .
But - I execute for my maven project command : mvn dependency:tree -Dverbose
and see following :
[INFO] +- org.seleniumhq.selenium:selenium-java:jar:3.0.1:compile
[INFO] | +- org.seleniumhq.selenium:selenium-chrome-driver:jar:3.0.1:compile
[INFO] | +- org.seleniumhq.selenium:selenium-edge-driver:jar:3.0.1:compile

With best regards,
Andrey

[andrey-epifanov]

@bonigarcia
After check I inclined to think that you are right, because without concrete version of chromedriver in setup I see in log :
2017-01-24 20:17:42 [main] INFO i.g.bonigarcia.wdm.BrowserManager - Reading http://chromedriver.storage.googleapis.com/ to seek chromedriver
2017-01-24 20:17:44 [main] INFO i.g.bonigarcia.wdm.BrowserManager - Latest version of chromedriver is 2.27
2017-01-24 20:17:44 [main] INFO i.g.bonigarcia.wdm.BrowserManager - Exporting webdriver.chrome.driver as C:\Users\Epifanov.m2\repository\webdriver\chromedriver\win32\2.27\chromedriver.exe

but this conflict of version is looking like trick, sorry ))

where can I watch matching versions chrome driver in seleniumhq and chromedriver in http://chromedriver.storage.googleapis.com/ ?