I'm trying to resolve an issue around what happens when one of our tests fail.
At the moment, if a test fails, Frank read_timeouts for approximately 120seconds before moving on the next test. From what I can tell this is linked to the default read_timeout (60s) not being overridden in either of the gateway.rb files in frank-cucumber.
I can override this by setting the read_timeout (http.read_timeout = 1) in both these files, but modifying the gems isn't a route I want to go down as it requires manual changes on a number of machines.
My question essentially, is if everybody else experiences this timeout, or is it something dumb we are doing on our end?
I'm trying to resolve an issue around what happens when one of our tests fail.
At the moment, if a test fails, Frank read_timeouts for approximately 120seconds before moving on the next test. From what I can tell this is linked to the default read_timeout (60s) not being overridden in either of the gateway.rb files in frank-cucumber.
frank-cucumber-1.2.2/lib/frank-cucumber/gateway.rb frank-cucumber-1.2.3/lib/frank-cucumber/gateway.rb
I can override this by setting the read_timeout (http.read_timeout = 1) in both these files, but modifying the gems isn't a route I want to go down as it requires manual changes on a number of machines.
My question essentially, is if everybody else experiences this timeout, or is it something dumb we are doing on our end?