KaneAI - World’s First E2E Software Testing Agent.Book a Demo Join TestMu Conference

How to use key_inputs method of Selenium.WebDriver Package

Best Selenium code snippet using Selenium.WebDriver.key_inputs

w3c_action_builder.rb

...95      # Retrieves the current KeyInput device96      #97      # @return [Selenium::WebDriver::Interactions::InputDevice] current KeyInput device98      #99      def key_inputs100        @devices.select { |device| device.type == Interactions::KEY }101      end102      #103      # Creates a pause for the given device of the given duration. If no duration is given, the pause will only wait104      # for all actions to complete in that tick.105      #106      # @example Send keys to an element107      #108      #   action_builder = driver.action109      #   keyboard = action_builder.key_input110      #   el = driver.find_element(id: "some_id")111      #   driver.action.click(el).pause(keyboard).pause(keyboard).pause(keyboard).send_keys('keys').perform112      #113      # @param [InputDevice] device Input device to pause...

action_builder.rb

Source: action_builder.rb

...95      # Retrieves the current KeyInput device96      #97      # @return [Selenium::WebDriver::Interactions::InputDevice] current KeyInput device98      #99      def key_inputs100        @devices.select { |device| device.type == Interactions::KEY }101      end102      #103      # Creates a pause for the given device of the given duration. If no duration is given, the pause will only wait104      # for all actions to complete in that tick.105      #106      # @example Send keys to an element107      #108      #   action_builder = driver.action109      #   keyboard = action_builder.key_input110      #   el = driver.find_element(id: "some_id")111      #   driver.action.click(el).pause(keyboard).pause(keyboard).pause(keyboard).send_keys('keys').perform112      #113      # @param [InputDevice] device Input device to pause...

key_inputs

Using AI Code Generation

1driver.find_element(:name, 'q').send_keys "Selenium WebDriver"2driver.find_element(:name, 'btnG').click3driver.find_element(:name, 'q').send_keys "Selenium WebDriver"4driver.find_element(:name, 'btnG').click5driver.find_element(:name, 'q').send_keys "Selenium WebDriver"6driver.find_element(:name, 'btnG').click7driver.find_element(:name, 'q').send_keys "Selenium WebDriver"8driver.find_element(:name, 'btnG').click9driver.find_element(:name, 'q').send_keys "Selenium WebDriver"10driver.find_element(:name, 'btnG').click11driver.find_element(:name, 'q').send_keys "Selenium WebDriver"12driver.find_element(:name, 'btnG').click13driver.find_element(:name, 'q').send_keys "

key_inputs

Using AI Code Generation

1driver.key_down(:control)2driver.key_down(:shift)3driver.key_down(:alt)4driver.key_down(:meta)5driver.key_down(:command)6driver.key_up(:control)

key_inputs

Using AI Code Generation

1driver.find_element(:name, 'q').send_keys 'selenium webdriver'2driver.find_element(:name, 'q').clear3driver.find_element(:name, 'q').send_keys 'selenium webdriver', :enter4driver.find_element(:name, 'q').send_keys 'selenium webdriver', :tab

key_inputs

Using AI Code Generation

1driver.key_inputs('Selenium')2driver.key_inputs(:enter)3driver.key_inputs('Selenium')4driver.key_inputs(:enter)5driver.key_inputs('Selenium')6driver.key_inputs(:enter)7driver.key_inputs('Selenium')8driver.key_inputs(:enter)

key_inputs

Using AI Code Generation

1driver.find_element(:name, 'q').send_keys 'selenium webdriver'2driver.action.send_keys(:return).perform3driver.find_element(:name, 'q').send_keys 'selenium webdriver'4driver.action.send_keys(:enter).perform5driver.find_element(:name, 'q').send_keys 'selenium webdriver'6driver.action.send_keys("\n").perform7driver.find_element(:name, 'q').send_keys 'selenium webdriver'8driver.action.send_keys("\r").perform9driver.find_element(:name, 'q').send_keys 'selenium webdriver'10driver.action.send_keys("\r").perform

key_inputs

Using AI Code Generation

1driver.key_inputs('Selenium')2driver.key_inputs(er)3driver.key_inputs('Selenium')4driver.key_inputs(:enter)5driver.key_inputs('Selenium')6driver.key_inputs(:enter)7driver.key_inputs('Selenium')8driver.key_inputs(:enter)

key_inputs

Using AI Code Generation

1driver.key_down(:control)2driver.key_down(:shift)3driver.key_down(:alt)4driver.key_down(:meta)5driver.key_down(:command)6driver.key_up(:control)

StackOverFlow community discussions

Questions

Discussion

ruby selenium web driver - get google knowledge graph content

checkbox - Want to select a particular record for editing by selecting a checkbox. ID is dynamic so need someidea to search by Name

Selenium ReadTimeout error while logging in

Live stream video of Selenium scripts/bots

Selenium > Web Drive : how to find a nested element by xpath (ruby)

I want to learn how to make a large script into smaller scripts which work together using the Page Object Model structure

How to test if content is visible, not hidden by scroll bar in Capybara/Selenium

Capybara::InfiniteRedirectError on visit('http://google.com')

Scrolling in android using Appium + Ruby

Ruby Selenium Webdriver - configuring Sauce Labs Pass/Fail

Apparently css won't know where to find xpdopen class by it's own, you have to give the entire path to the element:

Xpath:

content = @driver.find_element(:xpath, "//*[@id="rhs_block"]/ol/li/div[1]/div")

Css:

content = @driver.find_element(:css, "#rhs_block > ol > li > div.kp-blk._Jw._Rqb._RJe > .xpdopen")

https://stackoverflow.com/questions/30872109/ruby-selenium-web-driver-get-google-knowledge-graph-content

If your HTML is like:

<html>
       <input type=checkbox>
       <a>Janine</a>
</html>

You can use the following XPATH to select the checkbox for near to Janine

xpath=//a[contains(text(),'Janine')]/preceding-sibiling::input

If your checkbox comes after the anchor element like:

<html>
    <a>Janine</a>
    <input type=checkbox>   
</html>

you can use

xpath=//a[contains(text(),'Janine')]/following-sibling::input

You can learn more about these here

https://stackoverflow.com/questions/6142422/checkbox-want-to-select-a-particular-record-for-editing-by-selecting-a-checkbo

As asked for in the comments. The timeout can be increased by doing this:

client = Selenium::WebDriver::Remote::Http::Default.new
client.timeout = 240 # Or whatever you need
driver = Selenium::WebDriver.for :chrome, :http_client => client

https://stackoverflow.com/questions/62101638/selenium-readtimeout-error-while-logging-in

I got it working. Here's the updated Ruby script:

require 'capybara/dsl'
require 'selenium-webdriver'
require 'headless'

Capybara.configure do |c|
  c.javascript_driver = :selenium
  c.default_driver = :selenium
end

Capybara.register_driver :selenium do |app|
  profile = Selenium::WebDriver::Chrome::Profile.new
  profile['general.useragent.override'] = Bot::USER_AGENT
  Capybara::Selenium::Driver.new(app, {
    browser: :chrome,
    profile: profile,
    args: ["--window-size=1024,768"]
  })
end

class Bot
  include Capybara::DSL

  USER_AGENT = 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36'
  FILE_PATH = File.join(__dir__, 'segment%05d.ts')

  def run
    headless = Headless.new(video: {
      codec: 'libx264',
      frame_rate: 25,
      tmp_file_path: FILE_PATH,
      extra: [
        '-pix_fmt yuv420p',
        '-profile:v baseline',
        '-b:v 1500k',
        '-x264opts keyint=25',
        '-s 640x360',
        '-map 0',
        '-flags',
        '-global_header',
        '-f segment',
        '-segment_list index_1500.m3u8',
        '-segment_time 1',
        '-segment_format mpeg_ts',
        '-segment_list_type m3u8',
        '-segment_list_flags +live',
        '-segment_list_size 2',
      ],
    })
    headless.start
    headless.video.start_capture

    loop do
      print 'loading google... '
      visit('http://google.com')
      puts 'done'
      print 'loading youtube... '
      visit('http://youtube.com')
      puts 'done'
    end
  end
end

bot = Bot.new
bot.run

Internally, headless will build this command:

/usr/bin/avconv -y -r 25 -s 1280x1024 -f x11grab -i :99 -g 600 -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -b:v 1500k -x264opts keyint=25 -s 640x360
 -map 0 -flags -global_header -f segment -segment_list index_1500.m3u8 -segment_time 1 -segment_format mpeg_ts -segment_list_type m3u8 -segment_list_flags +li
ve -segment_list_size 2 /home/mhluska/record-test/segment%05d.ts

I'm not well versed in ffmpeg so I can't explain what half of these parameters do. The end result is it will produce segment*.ts files and index_1500.m3u8 which seems to be a manifest.

We can play it in the browser now. Create index.html:

<!doctype html>
<html>
  <head>
    <title>Video stream test</title>
  </head>
  <body>
    <video src="index_1500.m3u8" autoplay controls type="application/x-mpegURL"></video>
  </body>
</html>

And serve it temporarily with sudo python -m SimpleHTTPServer 80.

Notes/caveats:

I had to first set up a swap file on my VPS otherwise the script would get killed
The video tag seems to only play on Safari and not Chrome
The video ratio/size seems wrong but this can be corrected by tweaking the ffmpeg parameters

https://stackoverflow.com/questions/44469397/live-stream-video-of-selenium-scripts-bots

Okay! You can also use #css or #xpath as below:

@driver.find_elements(:css,"div#international-map a").map(&:text)
# => [" link a1 ", " link a2 ", " link a3 ", " link b1 ", " link b2 "]

@driver.find_elements(:xpath,"//div[@id = 'international-map']//a").map(&:text)
# => [" link a1 ", " link a2 ", " link a3 ", " link b1 ", " link b2 "]

https://stackoverflow.com/questions/17068354/selenium-web-drive-how-to-find-a-nested-element-by-xpath-ruby

This is quite a big question really! There are so many different approaches to the page object model - I'll try to give you an example that sorta fits with the code that you posted. It won't cover 100% what you need, but should give you an idea of the sort of thing you can do.

Firstly, you need to abstract your browser stuff. You want tests themselves to be build of page object calls and no direct calls to the browser itself. This means that you can change the stuff behind the scenes without having to edit your tests.

#
# The web browser.
#
module Browser
  #
  # Starts the browser.
  #
  # @return [Void]
  def self.start
    @browser ||= Selenium::WebDriver.for :chrome
  end

  #
  # Closes the browser.
  #
  # @return [Void]
  def self.close
    @browser.quit
  end

  private

  #
  # A catch all method to pass WebDriver requests through to our browser object.
  #
  # @return [Void]
  def self.method_missing(method, *arguments)
    @browser.send(method, *arguments)
  end
end

This provides us with a basic way of talking to the browser. We can start and stop it, and also run Selenium WebDriver methods through this module.

Next a basic page object module:

# Basic page object module. You will expand upon this a lot.
#
module PageObject
  #
  # Creates a class method that will return the selector and reference
  # of an element
  #
  # @param name [Symbol] name of the method
  # @param params [Hash<String>] element selector (key) and reference (value)
  def element(name, params)
    send(:define_method, name) do
      params
    end
  end

  #
  # Types into specified element.
  #
  # @param element [Hash] the element selector and reference
  # @param text [String] the text to type
  def type(element, text)
    Browser.find_element(element).send_keys text
  end

  #
  # Clicks on the specified element.
  #
  # @param element [Hash] the element selector and reference
  # @return [Void]
  def click(element)
    Browser.find_element(element).click
  end
end

Next an example page object. I've used your example of the login page.

#
# Page object representing a log in page. This is the bit that will contain all
# methods related to specific pages.
#
class LogInPage
  include PageObject

  element :email_field, id: 'email'
  element :password_field, id: 'password'
  element :submit_button, css: '.button.primary'

  #
  # Logs in using the specified user credentials.
  #
  # @param email [String] the users email address
  # @param password [String] the users password
  # @return [Void]
  def log_in_with!(email, password)
    type email_field, text: email
    type password_field, text: password
    click submit_button
    # Some approaches will return another page object at this point.
    # You can do this if you want, but personally I think it leads to confusing
    # tests.
  end

  #
  # Checks if a user is logged in.
  #
  # @return [Boolean]
  def user_logged_in?
    # This should return true or false depending on if a user is logged in.
    # Login page may not be the correct place for this, but it'll do for this
    # example.
  end
end

Your test might look something like:

describe 'Merchantcentric' do
  context 'User Login' do
    before :all do
      Browser.start
      Browser.get 'https://meffff.com/session/new'
      # Ideally all this browser creation stuff would be abstracted
      # out of your tests and into something else (spec_helper maybe?)
      @page = LogInPage.new
    end

    after :all do
      Browser.close
    end

    it 'success' do
      # I purposely left out your csv stuff - you should probably
      # have that separate to your tests also. I am assuming that
      # user and pass will be coming from somewhere.
      @page.log_in_with! user, pass
      assert(@page.user_logged_in?, 'User was not logged in successfully')
    end
  end
end

These would all obviously be inside different files! I've run out of lunch break time now, so if you have any questions let me know, I'm always available to chat about this stuff! Also apologies if some of this stuff doesn't work... I wrote it without testing but it should be ok(ish)!

Also, you shouldn't need to check for element presence before you interact with them. If the element isn't there, the test should fail anyway with a Selenium exception.

What made you settle on Rspec for your functional browser tests btw? Did you explore other options such as Cucumber?

Update

In regard to your comment:

In the example you've given, you could create a new method in your PageObject class called element_exists? and create a method inside your LogInPage class (for example) called deals_present?. You'd use this method in your assertion.

Your element_exists? method would be simple:

#
# Checks if an element exists, returning true or false.
#
# @params params [Hash] the selector and reference for the element
# @return [Boolean]
def element_exists?(params)
  Browser.find_elements(params).any?
end

Your ‘deals_present’ method could look something like:

#
# Checks if the deals element is present on the page.
#
# @return [Boolean]
def deals_present?
  element_exists? deals_navigation
end

You’d obviously need to create the deals_navigation page element using the ‘element’ method described in my post.

I notice that you want to have a wait.until before you check for the deals element. Again, you’ll want to abstract this out into your PageObject class and then perhaps call it inside your deals_present? method. I’ll let you work this one out, but let me know if you have too much trouble with it.

Your test assertion with all this done would look something like:

expect(!@page.deals_present?)

This will fail if the deals element is displayed. The benefit of doing it this way is you're removing the majority of the logic from the tests themselves which means if the logic changes, you just need to update it in a single place rather than all the tests that use it.

https://stackoverflow.com/questions/32366333/i-want-to-learn-how-to-make-a-large-script-into-smaller-scripts-which-work-toget

Have you tried using the find command, instead of page.has_content?

You should be able to pass in the abbreviations you already use and Capybara should (by default) ignore anything it cannot see (for example, if it is off the screen).

There's also a setting you can use to ensure that Capybara ignores hidden elements, although I believe this is the default behaviour:

Capybara.ignore_hidden_elements = true

As an aside, I'd avoid using !page.has_content? anywhere in your tests as Capybara will wait for your default timeout to be reached before returning anything. There's a page.has_no_content? method that does just that and will return as soon as the content is not there, saving you valuable time.

https://stackoverflow.com/questions/24481032/how-to-test-if-content-is-visible-not-hidden-by-scroll-bar-in-capybara-selenium

I fixed it thanks to this post: https://gist.github.com/pranav7/0f377b91a8b2cafe71bd

I needed to put this in features/support/env.rb

require 'cucumber/rails'
require 'capybara/cucumber'

Capybara.register_driver :chrome do |app|
  client = Selenium::WebDriver::Remote::Http::Default.new
  client.timeout = 120
  Capybara::Selenium::Driver.new(app, :browser => :chrome, :http_client => client)
end

Capybara.default_driver = :chrome

https://stackoverflow.com/questions/38093791/capybarainfiniteredirecterror-on-visithttp-google-com

I created a method to scroll to an element that is not on screen yet, because scroll_to was not working for me. This methos scrolls to any element on screen even if its not visible yet

def scroll_to_element(class_name, element_name)
  ele_by_json(typeArray: [class_name], onlyVisible: false, name: {target: element_name, substring: false, insensitive: false})
end

https://stackoverflow.com/questions/38869509/scrolling-in-android-using-appium-ruby

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

https://stackoverflow.com/questions/22617768/ruby-selenium-webdriver-configuring-sauce-labs-pass-fail

Blogs

Check out the latest blogs from LambdaTest on this topic:

Here Is How You Setup Perfect Cross Browser Testing Environment

Development of a website takes a lot of effort. You must be familiar with it if you have developed one. Even if I don’t consider the complexities of JQuery and other famous libraries of JavaScript. Only basic CSS, JS and HTML which are required to develop a complete website takes a lot of your time and hard work.

Cross Browser Automation Testing Using Watir

We are living in an era where software development demands for automation. Software development methodologies such as RAD(Rapid Application Development), Agile and so on requires you to incorporate automation testing as a part of your release cycle. There exist numerous test automation frameworks used for automation testing. Today, I will be picking up Watir an open source, selenium-based web driver used for browser automation. Cross browser automation testing using Watir would help you to ensure a good rendering user interface of your web app. If you are a beginner to automation testing and are unaware of basics then don’t worry as I will also be talking about browser automation, cross browser automation, parallel testing and what makes Watir special than other several tools and libraries. Without further ado, here we go!

How Pro-Testers Use CSS Selectors In Selenium Automation Scripts?

This article is a part of our Content Hub. For more in-depth resources, check out our content hub on Selenium Locators Tutorial.

Best Usability Testing Tools For Your Website

When a user comes to your website, you have time in seconds to influence them. Web usability is the key to gain quick trust, brand recognition and ensure user retention.

Top 5 Java Test Frameworks For Automation In 2019

For decades, Java has been the most preferred programming language for developing the server side layer of an application. Although JUnit has been there with the developers for helping them in automated unit testing, with time and the evolution of testing, when automation testing is currently on the rise, many open source frameworks have been developed which are based on Java and varying a lot from JUnit in terms of validation and business logic. Here I will be talking about the top 5 Java test frameworks of 2019 for performing test automation with Selenium WebDriver and Java. I will also highlight what is unique about these top Java test frameworks.

Automation Testing Tutorials

Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.