How to use handler method of Selenium.WebDriver.SpecSupport Package

Yes, this is possible.

Just add your chromedriver.exe binary to the project directory, then when you run your tests, be sure to use relative paths.

In Java, it would look something like this.

src/
  main/
    tests/
      MyTest.java
chromedriver.exe

Then the test would look like:

...
System.setProperty("webdriver.chrome.driver", "chromedriver.exe");
...

In ruby, I assume it'd be something similar.

Also, if you intend to do something like this, i'd recommend stating the version in the executable. For example: chromedriver-2.39.0.exe

In my case it helped to add the following to my Gemfile

# in test group
gem 'selenium-webdriver'

Then run bundle install

As I have no your code, assume we are testing https://encodable.com/uploaddemo/

@driver.navigate.to "https://encodable.com/uploaddemo/"
element = @driver.find_element(:css, 'input[type=file]')
element.send_keys   "/full/path/to/file.jpg"
@driver.find_element(:css, 'input[type=button]').click

So, you should send the full path to the input field and press the "submit" button

I would advise setting an ENV variable in your Rakefile before each test is run, like this:

ENV['TIMESTAMP_CONTROL'] = Time.now.to_s

You can then reference the variable anywhere in your scripts and Rakefile until you reset it again like any other Ruby variable:

assert_equal ENV['TIMESTAMP_CONTROL'], @email_response_text

I'm guessing you upgraded to the latest selenium-webdriver and chromedriver in the last few weeks. chromeOptions is no longer a valid key to pass, you can try changing it to goog:chromeOptions but you really should just be using an instance of the Selenium::WebDriver::Chrome::Options class

Capybara.register_driver :chrome do |app|
  options = ::Selenium::WebDriver::Chrome::Options.new
  options.binary = ...
  Capybara::Selenium::Driver.new(app, browser: :chrome, options: browser_options)
end

Selenium has a bug using css to locate elements in IE. If you switch to using a different browser (such as Firefox) you should see a vast improvement in performance.

To enable Flash before each test and WhiteList the url you can use the following code block to configure the WebDriver instance to allow Flash:

ChromeOptions options = new ChromeOptions();
Map<String, Object> prefs = new HashMap<String, Object>();
prefs.put("profile.default_content_setting_values.plugins", 1);
prefs.put("profile.content_settings.plugin_whitelist.adobe-flash-player", 1);
prefs.put("profile.content_settings.exceptions.plugins.*,*.per_resource.adobe-flash-player", 1);
prefs.put("PluginsAllowedForUrls", "https://your_url.com");
options.setExperimentalOption("prefs", prefs);
WebDriver driver = new ChromeDriver(options);

Here you can find a detailed discussion on Manage Flash in Chrome and on PluginsAllowedForUrls

Update :

You haven't mentioned in your comment through which client you are not able to find setExperimentalOption or set_experimental_option. Here is the snapshot from my IDE which have no errors/warnings :

And here is the JavaDoc :

You must be in the same domain to set the cookie. From the W3C specs

If the current browsing context’s document element is a cookie-averse Document object, return error with error code invalid cookie domain.

It's also explained in invalid cookie domain

An illegal attempt was made to set a cookie under a different domain than the current page.

A workaround will be to simply refresh the page after setting the cookie in the domain

b = Watir::Browser.new(driver)
b.goto('http://www.example.com')
b.cookies.add('foo', 'Hello, world!', domain: 'www.example.com')
b.refresh

It is possible for you to try the send_keys method. In your case, it would be something like this:

wait.until do
  waiting = driver.find_element id: "logo"
  waiting.send_keys :control, :subtract
end

In this example, you can send the keys when the element with the id of logo is found by Selenium when the page is fully loaded.