You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I must admit, I tried to read through the Navigation section, but could not find the exact reason for my problem. I have an idea but don't know exactly why. At first here is my problem:
I have a testscript in which I execute the following steps:
create a session
set implicitWait to 0
set pageLoadTimeout to 120 seconds
go to 'http://www.page-that-takes-long-to-load.com'
click on a link
wait until the url has changed
navigate back
assert that a specific element is present
The last steps fails, because the element could not be found. If i change the testscript to:
create a session
set implicitWait to 0
set pageLoadTimeout to 120 seconds
go to 'http://www.page-that-takes-long-to-load.com'
click on a link
wait until the url has changed
go to 'http://www.page-that-takes-long-to-load.com' <-- Only this line has changed
assert that a specific element is present
If yes, would it be possible to add to the specification, that the remote should also wait for the navigation to complete before returning with success when executing a Back- or Forward-command?
The text was updated successfully, but these errors were encountered:
I must admit, I tried to read through the Navigation section, but could not find the exact reason for my problem. I have an idea but don't know exactly why. At first here is my problem:
I have a testscript in which I execute the following steps:
The last steps fails, because the element could not be found. If i change the testscript to:
The browser is able to locate the element.
I think the reason for the difference is, that the Go command waits for the navigation to complete and returns afterwards. But the Back command returns after the pageShow event was fired.
My assumption is, that the pageShow event gets fired before event A (When event A is the event that leads the wait for the navigation to complete-procedure to return).
Am I correct with that assumption?
If yes, would it be possible to add to the specification, that the remote should also wait for the navigation to complete before returning with success when executing a Back- or Forward-command?
The text was updated successfully, but these errors were encountered: