TimeoutError is actually Capybara::TimeoutError, which is unrelated to Ruby's Timeout
…d clear up description.
…bara.insert_port_into_portless_url is true.
Thanks to Adam Cigánek for his helpful input and the original patch!
In order to run Selenium via Capybara on my virtual machine, you need to be able to bind the server IP to a net interface on the same subnet as the VM. This patch exposes an configuration variable to allow you to bind the test server to any net interface on your local machine. Falls back to 127.0.0.1 if the config var is not set.
…rt| ...} For example, to use mongrel rather than thin or webrick: Capybara.server do |app, port| require 'rack/handler/mongrel' Rack::Handler::Mongrel.run(app, :Port => port) end
This reverts commit a8a4efc.
This protects against the race conditions which inevitably occur when booting multiple capybara servers (such as running specjour). TCPServer.new() will set recently opened sockets to SOCK_WAIT status to ensure that a certain amount of time elapses before they are reused.