Skip to content

Implicit / Explicit wait management #149

Closed
@itfranck

Description

@itfranck

implicit waiting for elements to appear is disabled by default and will need to be manually enabled on a per-session basis. >Mixing explicit waits and implicit waits will cause unintended consequences, namely waits sleeping for the maximum time even >if >the element is available or condition is true.

Implicit wait being on by default, we need to temporarily disable it when Explicit wait are used to avoid the "unintended consequences"

Expected flow

  • Implicit wait get disabled
  • Explicit wait get applied (eg: waiting for timeout or specific condition to occurs)
  • Implicit wait get enabled again to its configured value

Currently affected cmdlets are :

  • Wait-SeDriver (V4.0)
  • Wait-SeElement (V4.))
  • Get-SeElement (with -Timeout parameter)
  • Clear-SeAlert

I Observed a few consequences, namely

  • Extended timeout (3 seconds timeout take varying longer amount of time)
  • Driver never return (It happened with ByChained queries and was locally fixed)

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions