Unable to download chrome webdriver

[Mo0rBy]

What happened?

I am attempting to run FE tests locally before trying to get them running in a CI/CD context. I've updated the pom.xml to use the latest version available (4.0.15) and when I try to run an FE test I get the following error:

WARNING: There was an error managing chrome (error sending request for url (https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/118.0.5993.70/mac-arm64/chromedriver-mac-arm64.zip): error trying to connect: tcp connect error: Operation timed out (os error 60)); using driver found in the cache

Then the tests try and use whatever webdriver I have cached somewhere which (surprise surprise) doesn't work. I had a quick look at the Chrome for Testing dashboard and I can see that the URL in the terminal does not match the URL on that site. The difference is at the end of the url (mac-arm64/chromedriver-mac instead of mac-arm64/chrome-mac)

In my terminal: ...../118.0.5993.70/mac-arm64/chromedriver-mac-arm64.zip

On the Chrome for Testing dashboard: ......./118.0.5993.70/mac-arm64/chrome-mac-arm64.zip

Screenshot of the Chrome for Testing dashboard as proof:

I'm assuming this is something that needs to be changed in the WebDriverManager package, or Serenity needs to be updated to use the version of this package that has this correction in.

I haven't got a clue when this URL change will have occurred as the last time I look at our testing repository was 2 months ago, and it was working then.

Are there any recommendations on how to get this working again? I believe the best thing would be to add the WebDriverManager as a dependency and use my own configured webdriver instead of what Serenity autodownloads and configures.

What did you expect to happen?

No response

Serenity BDD version

4.0.15

JDK version

openjdk version "17.0.6" 2023-01-17

Execution environment

Macbook Air M1, macOS Ventura 13.6

Chrome (v118, but trying to get anything working)

How to reproduce the bug.

Write an FE test (I guess it could be super simple and just attempt to search something on Google)
Configure a chrome webdriver in serenity.conf or serenity.properties
Run the test and observe the failure

How can we make it happen?

Add it to the Serenity BDD backlog and wait for a volunteer to pick it up

[wakaleo]

Serenity no longer uses WebDriverManager or automatic driver downloads - that's all done by Selenium now.

[Mo0rBy]

Ah ok. So I suppose the same question applies. Does Serenity need to be updated to use the latest Selenium version to use the updated URL? Or is that download URL set somewhere within Serenity?

[wakaleo]

No, Serenity pretty much always uses the latest versions. I think this is a Selenium issue, not a Serenity one.

[Mo0rBy]

I thought that would be the case. I imagine this URL change must be really recent, but as I said, I haven't been in the testing sphere for a couple of months, so I have no idea. I know the Chrome for Testing change was quite big and was difficult to deal with.

I'll open an issue within the Selenium Github and see what happens. Thanks @wakaleo!