Explicit timeout not waiting the full amount of time when loading new driver.
Opened this issue · 0 comments
itfranck commented
This should work flawlessly.
But it doesn't unless I add sleep time...
I need to investigate further.
I noticed a lot of small annoyances when testing in production context where I did need to wait-seelement or wait-sedriver a bit too much to my
Start-SeDriver -Browser Chrome -StartURL 'https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=13&ct=1607153201&rver=7.0.6737.0&wp=MBI_SSL&wreply=https%3a%2f%2foutlook.live.com%2fowa%2f%3fnlp%3d1%26RpsCsrfState%3dd87b1e47-26ba-c520-6763-f018d6646298&id=292841&aadredir=1&CBCXT=out&lw=1&fl=dob%2cflname%2cwld&cobrandid=90015' -Position 1920x0 -ImplicitWait 10
Get-SeElement -By TagName -Value input -Timeout 3
Start-SeDriver -Browser Chrome -StartURL 'https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=13&ct=1607153201&rver=7.0.6737.0&wp=MBI_SSL&wreply=https%3a%2f%2foutlook.live.com%2fowa%2f%3fnlp%3d1%26RpsCsrfState%3dd87b1e47-26ba-c520-6763-f018d6646298&id=292841&aadredir=1&CBCXT=out&lw=1&fl=dob%2cflname%2cwld&cobrandid=90015' -Position 1920x0 -ImplicitWait 10
Get-SeElement -By TagName -Value input -Timeout 3
This, in contrast, work fine
Start-SeDriver -Browser Chrome -StartURL 'https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=13&ct=1607153201&rver=7.0.6737.0&wp=MBI_SSL&wreply=https%3a%2f%2foutlook.live.com%2fowa%2f%3fnlp%3d1%26RpsCsrfState%3dd87b1e47-26ba-c520-6763-f018d6646298&id=292841&aadredir=1&CBCXT=out&lw=1&fl=dob%2cflname%2cwld&cobrandid=90015' -Position 1920x0 -ImplicitWait 10
Wait-SeElement -By TagName -Value Input -Condition ElementIsVisible
$Email = Get-SeInput -Type email
$Email
I definitely need to borrow a page from wait-seelement.