jnicklas/capybara — Issue #589: Drop Capybara.server_boot_timeout
Author: joliss
Created: 2012-01-03 20:29:23+00:00
State: open

/cc @madadam

Quoting my commit message in c444d336:

> Remove broken tests for server_boot_timeout
>
> When they were added in 09d6335, responsive? already only hit `/__identify__`, which does not hit the server, but gets special-cased in Capybara's Identify server class (and runs instantly).
>
> So it's not clear what constitutes a "slow" server that might time out at boot, and thus why server_boot_timeout needs to be configurable. A server that is slow to respond to HTTP requests would not trigger the boot timeout. All we really seem to be waiting for within the timeout window is for Thin or WEBrick to come up.

It's not clear to me at this point that this was ever a useful option. Should we perhaps remove it for Capybara 2.0? If it comes up for anyone, we can re-add it in 2.x, this time with proper tests to show why it's needed.