How to use process_w3c_options method of Selenium.WebDriver Package

Like the error is hinting, each DOM element can be referenced by its XPath which is similar, but more specific, than standard CSS selectors. You can the Path within the Chrome inspector by right clicking on the specific node.

Be careful testing something that's too specific. It's likely going to be fragile and break often making a test that's hard to maintain.

Relevant capybara doc: http://www.rubydoc.info/github/jnicklas/capybara/master/Capybara/Node/Finders

I got the same error on MacOs 10.11.6 and the following solved the issue:

Find the chromedriver

~/P/m/web-automation (master ⚡↩) which chromedriver
/Users/mesutgunes/.rbenv/shims/chromedriver

Remove it

rm /Users/mesutgunes/.rbenv/shims/chromedriver

Try to re-link it, follow the instruction:

~/P/m/web-automation (master ⚡↩) brew link chromedriver
Linking /usr/local/Cellar/chromedriver/2.30...
Error: Could not symlink bin/chromedriver
Target /usr/local/bin/chromedriver
already exists. You may want to remove it:
  rm '/usr/local/bin/chromedriver'

To force the link and overwrite all conflicting files:
  brew link --overwrite chromedriver

To list all files that would be deleted:
  brew link --overwrite --dry-run chromedriver

Unzip the IEDriver.zip file in any folder, so that folder contains IEDriver file e.g you unzipped it in C:\Drivers\

• Copy path till that folder. means only C:\Drivers\
• Go to My Computer -> Properties -> Advanced Settings -> Environment Variables
• Under that in front of PATH paste our path i.e C:\Drivers\ at the end and before that put ;
• Apply the changes made
• Restart command prompt

I see two problems with the script:

1. You are trying to use private method of Element class. To open link you need to all element.click, not element.open: This should work

   driver.find_elements(:tag_name, "a")[0].click

2. Don't iterate through the links on the page an try to click them without assuring that you get back to initial page before the next click. Otherwise Selenium loses context and will give you following message:

   Selenium::WebDriver::Error::StaleElementReferenceError

This is for firefox 60+ and the new marionette/geckodriver.

After fiddling a lot, this is how I got it working with a custom profile:

$ xvfb-run firefox -CreateProfile test
options = Selenium::WebDriver::Firefox::Options.new # no profile specified here
options.add_argument "--profile"
options.add_argument "/home/jenkins/.mozilla/firefox/f0jecsmr.test"
@browser = Watir::Browser.new :firefox, options: options, driver_opts: {marionette_port: 2828}, **capabilities

It is close to how documentation suggests to do with python. It took reading the source to figure out these driver_opts though (or I didn't find relevant documentation).

HTH somebody.

Ok, I have found firefox has an option to disable number input field support: 'dom.forms.number'.

So if you add the following lines in your env.rb, number input gets disabled and tests work again.

Capybara.register_driver :selenium do |app|
  profile = Selenium::WebDriver::Firefox::Profile.new
  profile["dom.forms.number"] = false
  Capybara::Selenium::Driver.new(app, :browser => :firefox, :profile => profile)
end

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

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

Without all the code for the page, I can't test it on your specific page but I found a jQueryUI slider example page at https://jqueryui.com/slider/. There is a slider handle defined there and when I slid it, it worked. From the HTML, it looks like you are grabbing the slider (the control itself) and not the handle (knob). Have you tried grabbing the knob IMG tag and sliding it?

The x and y offsets are in px so 120 seems like a reasonable value but it will vary depending on the size of your slider.

As a side note, I would suggest that when you are locating an element by id that you find it using find element by id instead of by XPath. Finding things by XPath is very slow (in comparison) and not necessary when locating an element like this.