How to use task_name method of CrazyFun.Mappings Package

Just write a code as below :

wait = Selenium::WebDriver::Wait.new(:timeout => 1000) 
wait.until do
    # you can chose any key instead of :control      
    driver.action.key_down(:control).perform.nil?
end
# to release the key :control
driver.action.key_up(:control).perform

Look the documentation of key_down :

Performs a modifier key press. Does not release the modifier key - subsequent interactions may assume it's kept pressed. Note that the modifier key is never released implicitly - either #key_up(key) or #send_keys(:null) must be called to release the modifier.

Here is the original answer from Jonas Nicklas.

You need to require 'capybara/rspec' and set :type => :request.
See the Capybara README section on "Using Capybara with RSpec".
/Jonas

Here is a working example on Github.

:first-child should be part of the selector:

browser.find_element(:css,".formProperty.fpMandatory.fpUpdateable .off .collapsedView.Uncompleted .fpColValue .textFieldValueSelector.valueSelector  .integer:first-child").send_keys"1000"

To select each of the elements, you can use :nth-child(n), where n is the count of the item you want to interact with:

browser.find_element(:css,".formProperty.fpMandatory.fpUpdateable .off .collapsedView.Uncompleted .fpColValue .textFieldValueSelector.valueSelector  .integer:nth-child(1)").send_keys"1000"
browser.find_element(:css,".formProperty.fpMandatory.fpUpdateable .off .collapsedView.Uncompleted .fpColValue .textFieldValueSelector.valueSelector  .integer:nth-child(2)").send_keys"200"

Note: :nth-child(n) will not work with IE 7 or IE 8.

Hopefully the last edit:

I think you're going to need to use find_elements() for this case.

elements = browser.find_elements(:css,".formProperty.fpMandatory.fpUpdateable .off .collapsedView.Uncompleted .fpColValue .textFieldValueSelector.valueSelector  .integer")

elements[0].send_keys"1000"
elements[1].send_keys"200"

Edit to explain the failure of :nth-child(n) in this case:

So, your original HTML that you edited in looked like this:

<div id="tile381" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>
<div id="tile383" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>
<div id="tile385" class="formProperty fpCompleted fpMandatory " ktype="formProperty"></div>
<div id="tile387" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>
<div id="tile389" class="formProperty fpMandatory " ktype="formProperty"></div>
<div id="tile391" class="formProperty fpCompleted fpMandatory " ktype="formProperty"></div>
<div id="tile393" class="formProperty fpCompleted fpMandatory " ktype="formProperty"></div>
<div id="tile395" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>
<div id="tile397" class="formProperty fpMandatory " ktype="formProperty"></div>
<div id="tile399" class="formProperty fpMandatory " ktype="formProperty"></div>

When I tested :nth-child(2), it worked on this particular HTML. When I tried nth-child(3), it did not work.

If your HTML looked like this:

<div id="tile381" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>
<div id="tile383" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>
<div id="tile387" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>
<div id="tile395" class="formProperty fpMandatory fpUpdateable " ktype="formProperty"></div>

Then :nth-child(n) would work for all four cases that it should match.

Given the structure of your HTML, find_elements is the correct approach.

An example straight from Sauce Labs found here.

require 'rubygems'
require "test/unit"
require 'selenium-webdriver'

class ExampleTest < Test::Unit::TestCase
    def setup
        caps = Selenium::WebDriver::Remote::Capabilities.firefox
        caps.version = "5"
        caps.platform = :XP
        caps[:name] = "Testing Selenium 2 with Ruby on Sauce"

        @driver = Selenium::WebDriver.for(
          :remote,
          :url => "http://username-string:access-key-string@ondemand.saucelabs.com:80/wd/hub",
          :desired_capabilities => caps)
    end

    def test_sauce
        @driver.navigate.to "http://saucelabs.com/test/guinea-pig"
        assert @driver.title.include?("I am a page title - Sauce Labs")
    end

    def teardown
        @driver.quit
    end
end

Every time you reload the page (because you are going to other page and then going back or because you simple reloaded the page) your references to the links 'links=box.find_elements(:tag_name,"a")' are lost.

I would suggest a few changes in order to workaround this (might not be the best solution)

links = box.find_elements(:tag_name,"a").size links_counter = 0 while links_counter < links box = @driver.find_element(:xpath,".//*[@id='popular_cat']") current_link = box.find_elements(:tag_name,"a")[links_counter] links_counter += 1 puts "--------------------" puts "Value of all links is:#{current_link.text}" current_link.click puts "Title of page is :#{@driver.title}" @driver.get "http://shopping.rediff.com/?sc_cid=inhome_icon" end

I hope this helps you!

Best, Fernando

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.

Instead of this

driver.find_elements(:xpath => "//p").each do |r|
        puts "Cell Value: " + r.text

Please try this

driver.find_elements(:xpath => "//p").each do |r|
        puts "Cell Value: " + driver.execute_script("return arguments[0].innerHTML", r)

Please let me know if this work for you.

I was facing the same issue with chrome drivers. Following are the cases that I found could lead to this issue:

• Missing TEMP or TMP environment variables
• TEMP or TMP is mapped not to local NTFS drive
• Permission issue (if you are using user other than the logged in user)
• TEMP or TMP invalid path

In my case TEMP was mapped to C:\Users\MyUser\AppData\Local\Temp\MyFolder. So when the Temp folder got cleared, MyFolder folder also got deleted and chromedriver threw "Unknown error: cannot create temp dir for user data dir" . By creating a new folder with name "MyFolder" in Temp folder fixed my issue.

TEMP and TMP path can be verified at

My Computer -> Properties -> Advanced System settings -> Environment Variables -> Variables used for < your user >

Or else you can check it by entering "%temp%" in "Run" window.

Its better to check path using both ways because I have seen some cases where temp path set in environment variable and path of folder that opens on executing %temp% command via Run were different.

Hope it helps.

You need to use Firefox version 31.0.6 . Versions of Firefox after that don't have the native events support. If you need to use a later version of Firefox, then just make sure your test actions are all non-native, such as using a JavascriptExecutor to create a hover (instead of relying on native events in the firefox driver).