Skip to content

(@W-24154851) fix: use non-deprecated implicitlyWait(Duration) overload - #246

Merged
lizaiv77 merged 1 commit into
salesforce:devfrom
helenren:dev
Sep 15, 2026
Merged

lizaiv77 merged 1 commit into
salesforce:devfrom
helenren:dev

Conversation

@helenren

@helenren helenren commented Sep 15, 2026

Copy link
Copy Markdown
Collaborator

selenium-java 4.33 deprecated Timeouts.implicitlyWait(long, TimeUnit). Switch to the supported Timeouts.implicitlyWait(Duration) overload.

  • selenium-java 4.33 deprecated Timeouts.implicitlyWait(long, TimeUnit). Switch DriverAdapter to the supported Timeouts.implicitlyWait(Duration) overload.

    • DriverConfig.getImplicitTimeout() already returns Duration, so the value is passed through directly.
    • Drops the now-unused java.util.concurrent.TimeUnit import.

    Test plan

    • mvn clean compile -Dmaven.compiler.showDeprecation=true — no remaining Selenium timeout deprecation warnings
    • mvn test-compile -Dmaven.compiler.showDeprecation=true — clean

selenium-java 4.33 deprecated Timeouts.implicitlyWait(long, TimeUnit).
Switch to the supported Timeouts.implicitlyWait(Duration) overload.
@helenren
helenren requested review from lizaiv77 and salesforce-elizabeth and removed request for salesforce-elizabeth September 15, 2026 18:32
@lizaiv77
lizaiv77 merged commit a21b3e7 into salesforce:dev Sep 15, 2026
6 checks passed
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.

2 participants