How to use ault_content method of Selenium.WebDriver Package

Did you try Selenium Grid? I think it creates pretty good summary report which shows details you need. I may be wrong, as I didn't use it for quite a while.

  Capybara.register_driver :selenium do |app|
    Capybara.app_host = "http://google.com"
    Selenium::WebDriver::Firefox::Binary.path = ENV['CUSTOM_FF_PATH'] if ENV['CUSTOM_FF_PATH'].present?
    profile = Selenium::WebDriver::Firefox::Profile.new
    profile.assume_untrusted_certificate_issuer = ENV['SKIP_CERT_ISSUER'].present?
    profile['browser.download.dir'] = "#{Rails.root}/tmp/webdriver-downloads"
    profile['browser.download.folderList'] = 2 # implies custom location
    profile['browser.helperApps.neverAsk.saveToDisk'] = "text/csv,application/pdf,application/doc,application/docx,image/jpeg"
    profile.native_events = true
    Capybara::Selenium::Driver.new(app, :browser => :firefox ,:profile => profile)
       #Capybara::Selenium::Driver.new app, :profile => profile
  end

Try with this configuration

I don't have enough reputation to comment on jacksparrow007's answer, but in Ruby Selenium, his suggestion could be coded as:

profile = Selenium::WebDriver::Firefox::Profile.new
profile['browser.cache.disk.enable'] = false
profile['browser.cache.memory.enable'] = false
profile['browser.cache.offline.enable'] = false
profile['network.http.use-cache'] = false
Selenium::WebDriver.for :firefox, :profile => profile

Also:

page.driver.browser.close

Definitely works for Selenium, though it looks like possibly not for capybara-webkit.

As already mentioned Selenium doesn't explicitly support opening of tabs, however there are 'workarounds' such as...

require 'watir-webdriver'
browser = Watir::Browser.new :ff
browser.goto 'http://the-internet.herokuapp.com'
browser.link(:text, 'A/B Testing').click(:command, :shift)
browser.windows.last.use

This will open the link in a new tab (on a mac) and focus it

File inputs are often hidden for styling reasons, which makes them non-interactable. Because of that capybara'sattach_file has an option to make it easier to temporarily make the file input visible/interactable

page.attach_file field, file_path, make_visible: true

That will temporarily apply CSS { opacity: 1, display: 'block', visibility: 'visible' } to the file input element. If that CSS won't make the input visible you can set make_visible to a hash that will rather than true

$ irb
2.3.3 :001 > require 'selenium-webdriver'
 => true 
2.3.3 :002 > d = Selenium::WebDriver.for(:chrome)
 => #<Selenium::WebDriver::Driver:0x..fcc762e239318ca30 browser=:chrome> 
2.3.3 :003 > d.execute_script('return navigator.userAgent')
 => "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36" 
2.3.3 :004 > d.quit
 => nil 
2.3.3 :005 >
$

Not sure if this will work because Iframes run in a separate sandbox to normal frames because you can do cross site page calls and they may have their own JavaScript which you wont be able to interact with.

@selenium.wait_for_frame_to_load "iframe", "30000"

it may work if you run your tests in *chrome or *iehta but don't have anything at the moment to test with

It simply may be the case that the page didn't load because of some error. Could you try to error out with:

raise(@driver.page_source.to_s)

just before the find_element command?

This way you could make sure that the input field is actually on the page, as seen by Selenium.