List Methods of Selenium.WebDriver.KeyActions package of Selenium Framework

There is no Capybara built-in support for drag to a specific offset in an element, all element actions target the centers of elements. Since you're using selenium you can drop to the driver level and specify an offset, however it means you can't easily swap to another driver

page.driver.browser.action.
    click_and_hold(source.native).
    move_to(target.native, 50, 100).
    release.perform

For other people on MacOS:

brew cask install chromedriver

And you'll be good to go.

If using Homebrew 2.6.0 (released in 2020.12.01) or above, you should use:

brew install --cask chromedriver

This works to use an existing Firefox profile with Firefox 48+:

profile = Selenium::WebDriver::Zipper.zip('/path/to/profile/xxx.default')
caps = Remote::Capabilities.firefox(firefox_options: {profile: profile})
browser = Watir::Browser.new :firefox, desired_capabilities: caps

Ruby bindings do not yet fully support all of the features of Firefox profiles from the old Firefox Driver in the new geckodriver. If you need these additional features you can use Firefox <48 (I recommend installing Extended Support Release) and pass in marionette: false in capabilities.

Here is one option:

driver.switch_to.alert.accept rescue Selenium::WebDriver::Error::NoAlertOpenError

This will click OK on the alert if one is present, else it will fail gracefully (silently).

Adapted from CollectiveIdea and another source.

Works on OSX. Firefox 34.0.5

Spec:

  describe 'Download CSV' do
    let( :submission_email ){ 'foo@example.com' }
    let( :email_csv ){ "id,email,created_at\n1,#{ submission_email }," }

    specify do
      visit '/emails'
      expect( page ).to have_content 'Email Submissions'

      click_on 'Download CSV'

      expect( DownloadHelpers::download_content ).to include email_csv
    end
  end

Spec helper:

require 'shared/download_helper'

Capybara.register_driver :selenium do |app|
  profile = Selenium::WebDriver::Firefox::Profile.new
  profile['browser.download.dir'] = DownloadHelpers::PATH.to_s
  profile['browser.download.folderList'] = 2

  # Suppress "open with" dialog
  profile['browser.helperApps.neverAsk.saveToDisk'] = 'text/csv'
  Capybara::Selenium::Driver.new(app, :browser => :firefox, :profile => profile)
end

config.before( :each ) do
    DownloadHelpers::clear_downloads
end

shared/download_helper.rb:

module DownloadHelpers
  TIMEOUT = 1
  PATH    = Rails.root.join("tmp/downloads")

  extend self

  def downloads
    Dir[PATH.join("*")]
  end

  def download
    downloads.first
  end

  def download_content
    wait_for_download
    File.read(download)
  end

  def wait_for_download
    Timeout.timeout(TIMEOUT) do
      sleep 0.1 until downloaded?
    end
  end

  def downloaded?
    !downloading? && downloads.any?
  end

  def downloading?
    downloads.grep(/\.part$/).any?
  end

  def clear_downloads
    FileUtils.rm_f(downloads)
  end
end

You can use #evaluate_javascript to check this. Something along the lines of

in_view = evaluate_script("(function(el) {
  var rect = el.getBoundingClientRect();
  return (
    rect.top >= 0 && rect.left >= 0 &&
    rect.bottom <= (window.innerHeight || document.documentElement.clientHeight) &&
    rect.right <= (window.innerWidth || document.documentElement.clientWidth)
  )
})(arguments[0]);", find('div.footer'))
# assert that in_view is true, or whatever you want.

I had the same problem. After downgrading to firefox v33 everything worked fine again.

You can find the older versions here

I've seen a similar trace before and 2 potential causes for it:

1) gems like FakeWeb and WebMock modify ruby's http. Try removing those gems and any similar ones you may be using to mock/block web requests.

2) I've seen a case in a really loaded down system where this timeout would occur somewhat randomly. Really the issue here wasn't the test but the system and what was running on it. It's possible to change the timeout used by the http library and continue testing.

Updated for Capybara: (from )

Capybara.register_driver :selenium_extended_http_timeout do |app|
    client = Selenium::WebDriver::Remote::Http::Default.new
    client.timeout = 240
    Capybara::Selenium::Driver.new(app, 
                               :browser => :firefox, 
                               :http_client => client, 
                               :resynchronization_timeout => 60,
                               :resynchronize => true)                                                                   
end
Capybara.javascript_driver = :selenium_extended_http_timeout

There's a good chance you don't need the resynchronization stuff.

In both cases this is related to how selenium does some of its internal communications. The JsonWireProtocol.

Port 9515 is the default port for chromedriver, so the connection attempt to 127.0.0.1:9515 is selenium attempting to connect to chromedriver in order to control the browser (Chrome) - The error would tend to indicate that chromedriver isn't starting up correctly. Check you have the latest version of chromedriver installed (or at least one that is compatible with the version of Chrome you're using') and also update selenium-webdriver. If using the chromedriver-helper gem you need to do bundle exec chromedriver -v when checking which version you're actually using since it installs a shim that can end up with you using a different version than it would appear if you just ran chromedriver -v