Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selenium scripts are getting failed due to chrome driver compatible issue v75 #1340

Open
pradeepks780 opened this issue Oct 23, 2019 · 6 comments

Comments

@pradeepks780
Copy link

@pradeepks780 pradeepks780 commented Oct 23, 2019

As mentioned in the windows 2019, am using chrome driver v75 for triggering scripts, but which is getting failed due to compatible issue.

Can anyone please let me know the chrome browser version which is running on windows server 2019
image

@DanielHabenicht

This comment has been minimized.

Copy link

@DanielHabenicht DanielHabenicht commented Oct 23, 2019

You have to update the chromedrive to a matching version see:
https://stackoverflow.com/a/55201365/9277073

RELATED: #861

@pradeepks780

This comment has been minimized.

Copy link
Author

@pradeepks780 pradeepks780 commented Oct 24, 2019

You have to update the chromedrive to a matching version see:
https://stackoverflow.com/a/55201365/9277073
RELATED: #861

But Im not sure about the browser version which is running in windows server 2019

@DanielHabenicht

This comment has been minimized.

Copy link

@DanielHabenicht DanielHabenicht commented Oct 24, 2019

Than, a heartly welcome to the party! Nobody knows, could be anything between 75 and 78.

@pradeepks780

This comment has been minimized.

Copy link
Author

@pradeepks780 pradeepks780 commented Oct 24, 2019

Ten wats the solution for the issue which I am facing

@DanielHabenicht

This comment has been minimized.

Copy link

@DanielHabenicht DanielHabenicht commented Oct 24, 2019

Just try different chromedriver version for chrome 76 and 77. My best guess would be chrome 77 or 78

@koskila

This comment has been minimized.

Copy link

@koskila koskila commented Oct 25, 2019

I ran into this same issue this week - the version listed in the documentation is wrong. However, in case you're using YAML to configure your pipeline, you can find out the version of Chrome installed on the machine by adding this step:

  • powershell: |
    (Get-Item "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe").VersionInfo
    displayName: 'We want to know the Chrome version installed on this machine'

For me, it was 77, so I changed my WebDriver to be 77.0.3865.40. I suppose that's compatible with whatever's on the images now.

However, you should also be able to use the WebDriver already installed on the machine after you add it to PATH environment variable - again, in case you're using YAML to configure your pipelines, you can add the WebDriver's location to the PATH variable roughly like so:

  • pwsh: |
    echo "##vso[task.prependpath]$env:CHROMEWEBDRIVER"
    displayName: Adds ChromeWebDriver for Selenium to PATH

(CHROMEWEBDRIVER is an environment variable that should be set in the images by default).

This configuration got our pipeline to work, would be interested in hearing if it helps out anyone else! I posted a longer explanation with more code examples here:
https://www.koskila.net/how-to-use-the-right-version-of-the-webdriver-on-hosted-agents-in-azure-devops/

koskila pushed a commit to koskila/azure-pipelines-image-generation that referenced this issue Oct 27, 2019
Documentation has outdated version for Chrome and Chrome WebDriver. These version numbers have been checked from the latest image.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.