List Methods of Selenium.WebDriver.Remote.Http package of Selenium Framework

location_once_scrolled_into_view to scroll using ruby.
As per your question your element is not visible, so selenium web driver is unable to click on it.

Simple solution to this is:

1. Store the xpath of the element which is visible and nearby to your element.
2. Scroll till that visible element, to make your element visible.
3. Ensure your element is now visible, click on it

eg code:

  element = dirver.find_element(:xpath, "xpath of nearby visible element")
  element.location_once_scrolled_into_view
  my_element = driver.find_element(:xpath, "xpath of your element")
  my_element.click

The waiting for the page to load is controlled by the page load strategy. By default, it is set to "normal", which waits for the document readiness state to be "complete". You can set the strategy to "none" to remove the waiting. Some of the browsers/drivers also support an "eager" strategy that waits for the browser to be in the "interactive" state.

require 'webdrivers'
require 'watir'

browser = Watir::Browser.new :chrome, page_load_strategy: 'none'
browser.goto 'www.google.com'
p browser.ready_state
#=> "loading"

See https://w3c.github.io/webdriver/#navigation for more details.

You need to use #text method.

browser.find_element(:css,"#total > tbody > tr > td:nth-child(4) > span").text

attribute method is used to get the value of attributes of HTML elements. In your case, there is no attribute called 'value' in span element, thus the method returns nil. For more information read the documentation I linked.

A possible solution:

WebElement temp = driver.findElement(By.id("s"));
List<WebElement> opts = temp.findElements(By.xpath(".//option"));
for (WebElement opt : opts){
    if (opt.isEnabled()){
        // do something
    }
}

Try:

page.execute_script("$('#element').trigger('mouseenter')")

For a clean solution, you need to have capybara-webkit gem installed. In your spec_helper add:

RSpec.configure do |config|
  # ... Your configuration
  Capybara.javascript_driver = :webkit
end

With this you should be able to trigger events with:

page.find('#element').trigger(:mouseover)

Is it an element that doesn't appear right away? If so, try:

wait.until { driver.find_element(:css => "#HPSearchInput > form > input.ch-  btn.searchBtn").displayed? }
driver.find_element(:css => "#HPSearchInput > form > input.ch-  btn.searchBtn").

Based on the error message, it looks like switch_to_frame wants the frame element passed as a parameter. I believe you need to find the frame before you can pass it into this method.

So, replace this line @session.switch_to_frame("//*[@id=\"OF_jreport\"]") with these two lines:

# Find the frame
frame = @session.find("//*[@id=\"OF_jreport\"]")

# Switch to the frame
@session.switch_to_frame(frame)

Pass the test files you want to run as arguments of your rake task. How to pass arguments: How to pass command line arguments to a rake task

Justin, you have a good approach. But there is a gotcha in assuming that the window handles will return in the correct order. This isn't always the case across all browsers. I outline a slightly different approach in my free weekly Selenium tip newsletter (elemental-selenium.com).

It goes like this:

@driver.get 'http://the-internet.herokuapp.com/windows'
main_window = @driver.window_handle
@driver.find_element(css: '.example a').click
windows = @driver.window_handles
  windows.each do |window|
    if main_window != window
      @new_window = window
    end
  end
@driver.switch_to.window(main_window)  
@driver.title.should_not =~ /New Window/  
@driver.switch_to.window(@new_window)  
@driver.title.should =~ /New Window/  

You can see the full tip here.