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'm implementing the serenity latest version - 3.2.0 with cucumber. Earlier it was working fine for all sorts of validations like seeThat/Ensure. However, with the recent change to 3.2.0, the above validation calls are failing as they're not waiting for the action to complete.
Like in my case, when I click on Continue/Submit button, the user is navigated to a new page. But the call itself is failing before coming to the landing page. The implicit wait is above 10 seconds, and the page is loading in 4 seconds.
If I revert to the old versions, like 2.5.7 it works fine.
What makes you think it is not waiting? In version 3.2.0, isVisible() will use the webdriver.wait.for.timeout property to determine how long it will wait, with a default of 5 seconds. If you have any doubts, put a breakpoint in the IsVisibleMatcher to understand how the code works under the hood.
I'm implementing the serenity latest version - 3.2.0 with cucumber. Earlier it was working fine for all sorts of validations like seeThat/Ensure. However, with the recent change to 3.2.0, the above validation calls are failing as they're not waiting for the action to complete.
seeThat(WebElementQuestion.the({target-locators}), isCurrentlyVisible())
Like in my case, when I click on Continue/Submit button, the user is navigated to a new page. But the call itself is failing before coming to the landing page. The implicit wait is above 10 seconds, and the page is loading in 4 seconds.
If I revert to the old versions, like 2.5.7 it works fine.
Please suggest.
@wakaleo
The text was updated successfully, but these errors were encountered: