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.
I think it would be useful to have a waitFor like construct that refreshes the browser before each try. I think it would be the same in all other regards.
It should support nested use such as:
refreshWaitFor {
waitFor(1) {
// some condition
}
}
Based on my, somewhat hazy, understanding of how waitFor is implemented, that support for nesting would come for free.
The text was updated successfully, but these errors were encountered:
I think this method should probably on be on Browser, as Pages can have cached elements that are going to go stale. However, it's conceivable that the user is going to go on and make use of the page after doing this, so it might be beneficial to get a freshly loaded page out of it.
I decided against passing pages to refreshWaitFor() for it to handle navigating to them because there are 4 signatures of Browser.to() and 4 signatures of waitFor() and combining them in a meaningful way proved tricky. I went with my initial idea, hopefully it still makes things easier for you @ldaley and @timyates.
I think it would be useful to have a
waitFor
like construct that refreshes the browser before each try. I think it would be the same in all other regards.It should support nested use such as:
Based on my, somewhat hazy, understanding of how
waitFor
is implemented, that support for nesting would come for free.The text was updated successfully, but these errors were encountered: