Closed ankitsinghaniyaz closed 1 year ago
Any help would be appreciated on this.
Thank you for you kind proposal. I'm afraid that I don't know whether Capybara Selenium driver behaves similarly or not. Do you know how?
@YusukeIwaki, I didn't get your question. What do you mean?
I am sorry for late response. (I was very busy and don't afford to maintain this gem in these days...)
I checked the behavior of Capybara + Selenium, and it seems that visit
does not timeout even when Capybara. default_max_wait_time = 1
.
Selenium Webdriver timeouts after 30 seconds with a Net::ReadTimeout
exception. and Capybara doesn't provide a configuration for extend the read_timeout. Users must configure WebDriver directly to extend the read timeout.
My opinion is that we have to configure Playwright directly for extending visit
timeout on capybara-playwright-driver.
Oops, my misunderstanding...
Capybara::Selenium::Driver takes timeout
parameter for configure read_timeout.
https://github.com/teamcapybara/capybara/blob/master/lib/capybara/selenium/driver.rb#L70
Currently Capybara::Playwright::Driver uses the timeout
for chromium.launch(timeout:) and it is not compatible with Selenium driver.
The reasonable solution for this issue is to respect the timeout
for defining default navigation timeout.
I'm randomly getting this error in my tests
In my configuration I've increased the timeout to be 60000ms but still getting the same errors, seems like it's not respected?
Here's how my settings look like:
I've also set the max timeout
Any pointers would help.