-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
BrowserWebDriverContainer fails to determine Selenium version for Selenium 4 (alpha) #3607
Comments
I had the same problem, I have solved it like this (on Scala):
For Selenium 4 And I disabled the startup checks: |
Full example:
And Suite:
|
There has been a lot of changes on BrowserWebDriverContainer and AFAICS, the wait strategy implemented is like the one suggested. Also, selenium 4 is GA so there should not be issues around it. |
This seems like a similar issue to #611, except this time it's Selenium 4.
When using Selenium 4, the manifest in selenium-api-4.0.0-alpha-3.jar looks like this:
This means that
SeleniumUtils.java
ends up returning2.45
for the Selenium version (ie, the base case).This also means that we end up with a BrowserWebDriverContainer with Chrome version 40-something in it (I forget the exact version, but it's an old one). I tried passing in an explicit container name when constructing the BrowserWebDriverContainer, like this:
But this always ends up throwing a TimeoutException, for reasons I don't understand.
Thanks for any assistance and let me know if I can provide further info!
The text was updated successfully, but these errors were encountered: