Skip to content
Commits on Mar 17, 2013
  1. @jwilger
Commits on Mar 16, 2013
  1. @jwilger

    Server#responsive? now rescues all SystemCallError exceptions

    jwilger committed
    It previously only rescued Errno::ECONNREFUSED and Errno::EBADF. On a
    few occasions, I have also seen the Errno::ETIMEDOUT exception raised by
    Net::HTTP from this method. Since the Net::HTTP calls are the only thing
    in this method that should be making any kind of system calls, a rescue
    of all SystemCallError exceptions (the superclass of all of the Errno
    exceptions) will catch these as well as any other system call errors
    triggered by Net::HTTP.
Commits on Dec 26, 2012
  1. @jdelStrother

    Catch the correct timeout exception during Server#boot

    jdelStrother committed
    TimeoutError is actually Capybara::TimeoutError, which is unrelated to Ruby's Timeout
Commits on Jul 13, 2012
Commits on Jul 4, 2012
  1. @DouweM
Commits on Apr 23, 2012
  1. @DouweM
Commits on Apr 22, 2012
  1. @DouweM

    Insert port into URL to visit if it doesn't have one already and Capy…

    DouweM committed
    …bara.insert_port_into_portless_url is true.
Commits on Mar 6, 2012
  1. @raggi
Commits on Feb 1, 2012
Commits on Jan 8, 2012
  1. @joliss

    Remove Capybara.server_boot_timeout, hard-code 60 seconds. Closes #589

    joliss committed
    Thanks to Adam Cigánek for his helpful input and the original patch!
Commits on Jan 3, 2012
  1. @joliss

    Poll for the server coming up more frequently

    joliss committed
    Capybara.timeout sleeps 50ms between polls, and since the server tends
    to boot quickly, this is a reasonable value. By not adding another
    500ms, we shave a few seconds off the test execution time, mostly in
    spec/server_spec.rb.
Commits on Oct 28, 2011
  1. Merge pull request #516 from dbalatero/add_server_host_option

    committed
    This adds a server_host option to Capybara.
Commits on Oct 19, 2011
  1. @wisq

    Raise on Rack app timeout.

    wisq committed
Commits on Oct 5, 2011
  1. @dbalatero

    This adds a server_host option to Capybara.

    dbalatero committed
    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.
Commits on Apr 26, 2011
  1. @drogus
Commits on Nov 17, 2010
  1. @madadam
Commits on Nov 9, 2010
Commits on Oct 28, 2010
  1. Allow the Rack handler to be configured via Capybara.server {|app, po…

    John Firebaugh committed
    …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
Commits on Oct 8, 2010
  1. Use 127.0.0.1 instead of localhost

    committed
    Apparently this prevents some issues and has no
    downsides.
  2. Drop mongrel support, silence thin and webrick

    committed
    Mongrel is an outdated server, it doesn't work on
    Ruby 1.9, for speed, thin is perfectly well suited
    for compatibility webrick is much better.
    
    Also: no more annoying logging information from
    thin/webrick
Commits on Sep 2, 2010
  1. @vangberg
Commits on Jul 14, 2010
  1. Use TCPServer to find available port for server

    committed
    Reverts the revert.
    
    I've added some code to make the Server reuse already booted
    applications.
    
    This reverts commit 9fe037d.
    
    Conflicts:
    
    	lib/capybara/server.rb
Commits on Jul 11, 2010
Commits on Jul 10, 2010
  1. Move utils into own folder

    committed
Commits on Jul 9, 2010
  1. Explicit module for Server

    committed
  2. Rename WaitUntil to timeout

    committed
Commits on Jul 6, 2010
  1. @bernerdschaefer

    Use TCPServer to find available port for server

    bernerdschaefer committed
    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.
Commits on Mar 24, 2010
  1. @lucasprim

    MSWin Fix

    lucasprim committed
Commits on Mar 12, 2010
Commits on Feb 26, 2010
  1. Darrin Holst to contributors

    committed
Commits on Feb 19, 2010
Something went wrong with that request. Please try again.