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

fix(selenium): add backwards compatible way of settings various timeouts when using selenium 3 #482

Merged
merged 2 commits into from
Sep 26, 2024

Conversation

Zidious
Copy link
Contributor

@Zidious Zidious commented Sep 26, 2024

This PR adds adds a selenium 3 compatible fallback when we attempt to set the various timeouts.

  • Added a regression test to catch this
  • Found two unrelated issues (tagged in this commit that will require follow up shortly after)

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

@Zidious Zidious requested a review from a team as a code owner September 26, 2024 16:39
Comment on lines +209 to +216
<!-- 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>
Copy link
Contributor Author

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.

Copy link
Member

@stephenmathieson stephenmathieson left a 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?

@Zidious
Copy link
Contributor Author

Zidious commented Sep 26, 2024

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

@stephenmathieson
Copy link
Member

Is there an issue for tracking removing Selenium 3 support?

@Zidious
Copy link
Contributor Author

Zidious commented Sep 26, 2024

Is there an issue for tracking removing Selenium 3 support?

@Zidious Zidious merged commit c4a92d4 into develop Sep 26, 2024
17 checks passed
@Zidious Zidious deleted the fix-sel-3-nosuchmethod branch September 26, 2024 19:13
@github-actions github-actions bot mentioned this pull request Sep 26, 2024
michael-siek added a commit that referenced this pull request Sep 27, 2024
#
[4.10.0](v4.9.1...v4.10.0)
(2024-09-26)


### Bug Fixes

* **selenium:** add backwards compatible way of settings various
timeouts when using selenium 3
([#482](#482))
([c4a92d4](c4a92d4))


### Features

* Update axe-core to v4.10.0
([#471](#471))
([4ac66b6](4ac66b6))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: scriptTimeout does not exist on selenium 3.141.59
3 participants