How to use firefox method of Selenium.WebDriver Package

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
    }
}

Changing a webrat step from

When /^I press "([^\"]*)"$/ do |button|
  click_button(button)
end

to

When /^I press "([^\"]*)"$/ do |button|
  click_button(button)
  selenium.wait_for_page_to_load
end

it works. Telling selenium to wait fixes!

I post an RSpec test that simulate files drag and drop using Selenium webdriver. It use jQuery to make and trigger a fake 'drop' event.

This code simulate drag and drop of a single file. For sake of simplicity I've stripped code that allow multiple files dropping. Tell me if you need it.

describe "when user drop files", :js => true do
  before do
    page.execute_script("seleniumUpload = window.$('<input/>').attr({id: 'seleniumUpload', type:'file'}).appendTo('body');")

    attach_file('seleniumUpload', Rails.root + 'spec/support/pdffile/pdfTest.pdf')

    # Trigger the drop event
    page.execute_script("e = $.Event('drop'); e.originalEvent = {dataTransfer : { files : seleniumUpload.get(0).files } }; $('#fileDropArea').trigger(e);")
  end

  it "should ..." do
     should have_content '...'
  end

P.S.: remember to replace #fileDropArea with ID of your drop area.

P.P.S: don't use evaluate_script in place of execute_script, otherwise selenium get stuck evaluating complex jQuery objects!

UPDATE: I've write a method you can reuse and do the stuff written above.

def drop_files files, drop_area_id
  js_script = "fileList = Array();"
  files.count.times do |i|
    # Generate a fake input selector
    page.execute_script("if ($('#seleniumUpload#{i}').length == 0) { seleniumUpload#{i} = window.$('<input/>').attr({id: 'seleniumUpload#{i}', type:'file'}).appendTo('body'); }")
    # Attach file to the fake input selector through Capybara
    attach_file("seleniumUpload#{i}", files[i])
    # Build up the fake js event
    js_script = "#{js_script} fileList.push(seleniumUpload#{i}.get(0).files[0]);"
  end

  # Trigger the fake drop event
  page.execute_script("#{js_script} e = $.Event('drop'); e.originalEvent = {dataTransfer : { files : fileList } }; $('##{drop_area_id}').trigger(e);")
end

Usage:

describe "when user drop files", :js => true do
  before do
     files = [ Rails.root + 'spec/support/pdffile/pdfTest1.pdf',
               Rails.root + 'spec/support/pdffile/pdfTest2.pdf',
               Rails.root + 'spec/support/pdffile/pdfTest3.pdf' ]
     drop_files files, 'fileDropArea'
  end

  it "should ..." do
     should have_content '...'
  end
end   

It's very likely that your file has a byte-order mark U+FEFF at the very beginning. You are probably losing it when you copy and paste again.

The proper solution is:

CSV.foreach("foo.csv", "r:bom|utf-8") { ... }

One more solution (in Java, because you didn't tell us your language - but it works the same way in all languages with Keys class):

String selectAll = Keys.chord(Keys.CONTROL, "a");
driver.findElement(By.whatever("anything")).sendKeys(selectAll);

You can use this to select the whole text in an <input>, or on the whole page (just find the html element and send this to it).

For using Selenium Ruby bindings:

There's no chord() method in the Keys class in Ruby bindings. Therefore, as suggested by Hari Reddy, you'll have to use Selenium Advanced user interactions API, see ActionBuilder:

    driver.action.key_down(:control)
                 .send_keys("a")
                 .key_up(:control)
                 .perform

The value of an upload input field should be an absolute path to the file on your local machine, not a URL. Download the image first.

The Before hook is run before each scenario. This is why a new browser is opened each time.

Do the following instead (in the env.rb):

require "selenium-webdriver"

driver = Selenium::WebDriver.for :ie
accept_next_alert = true
driver.manage.timeouts.implicit_wait = 30
driver.manage.timeouts.script_timeout = 30
verification_errors = []

Before do
  @driver = driver
end

at_exit do
  driver.close
end

In this case, a browser will be opened at the start (before any tests). Then each test will grab that browser and continue using it.

Note: While it is usually okay to re-use the browser across tests. You should be careful about tests that need to be run in a specific order (ie become dependent). Dependent tests can be hard to debug and maintain.

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.

From MDN's URL documentation:

It is worth noting that the part after the #, also known as the fragment identifier, is never sent to the server with the request.

Check your server logs; you'll see that any request to /widget-web/#/ is sent as a request to /widget-web/. The # prevents anything after it from being sent to the server.

What is a URL? docs