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
Currently when using methods such as ClickAsync the timeout seems to be infinite unless specified through an options class when calling the method. I've had a look at the different timeout options on the Page object and also runsettings and these do not seem to impact the methods such as ClickAsync and ElementHandleAsync. I have however noticed that the NodeJS playwright has an ActionTimeout in the documentation https://playwright.dev/docs/test-timeouts#test-timeout
It would be great if we were able to set the action timeout in the runsettings file for our NUnit tests and potentially on the browser/page objects to prevent any potential test hangs and give feedback faster when creating tests if a locator is incorrect. Thanks
The text was updated successfully, but these errors were encountered:
Currently when using methods such as ClickAsync the timeout seems to be infinite unless specified through an options class when calling the method. I've had a look at the different timeout options on the Page object and also runsettings and these do not seem to impact the methods such as ClickAsync and ElementHandleAsync. I have however noticed that the NodeJS playwright has an ActionTimeout in the documentation https://playwright.dev/docs/test-timeouts#test-timeout
It would be great if we were able to set the action timeout in the runsettings file for our NUnit tests and potentially on the browser/page objects to prevent any potential test hangs and give feedback faster when creating tests if a locator is incorrect. Thanks
The text was updated successfully, but these errors were encountered: