-
Notifications
You must be signed in to change notification settings - Fork 101
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
fix(selenium): add backwards compatible way of settings various timeouts when using selenium 3 #482
Conversation
…uts when using selenium 3
<!-- https://mvnrepository.com/artifact/org.mockito/mockito-core --> | ||
<dependency> | ||
<groupId>org.mockito</groupId> | ||
<artifactId>mockito-core</artifactId> | ||
<!-- versions >4 require Java 11 --> | ||
<version>4.11.0</version> | ||
<scope>test</scope> | ||
</dependency> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly formatting changes - this test dependency is the new addition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We should really consider dropping support for Selenium 3, and do so quickly. Is this on the roadmap?
I believe this has been in discussion for the 5 release. As updating to the the later versions of Selenium 4 does require Java 11. So we'd need to think carefully whether we want to continue to support selenium 4.X on Java 8 or move to selenium >4 on Java 11 or both |
Is there an issue for tracking removing Selenium 3 support? |
|
This PR adds adds a selenium 3 compatible fallback when we attempt to set the various timeouts.
QA Notes: Using Selenium 3 it should analyze correctly there should also be no change to the existing behaviour when using selenium 4.
Closes: #479