How to use camelize method of Selenium.WebDriver Package

Here is an example Directly from the Docs on how to create a feature that would allow you to skip:

Given a file named "feature/test.feature"

Feature: test
  Scenario: test
    Given this step says to skip
    And this step passes

Using standard step defintions and with a file such as "features/step_definitions/skippy.rb" with:

Given /skip/ do
  skip_this_scenario
end

if you run cucmber -q then the previous would pass as:

Feature: test

  Scenario: test
    Given this step says to skip
    And this step passes

1 scenario (1 skipped)
2 steps (2 skipped)
0m0.012s

To implement something similar in Ruby, check out this page that goes over that. Thanks to lamont for letting me know in the comments.

You can start chrome using a specific Chrome profile. I am not sure what the ruby implementation would look like, but in python it looks something like:

from selenium import webdriver
from selenium.webdriver.chrome.options import Options as ChromeOptions

options = ChromeOptions()
# more on this line here later.
options.add_experimental_option('debuggerAddress', '127.0.0.1:7878')
driver = webdriver.Chrome(chrome_options=otpions)

In order for this to work you need to do a few things.

manually start chrome from terminal/command prompt with these command line arguments --user-data-dir=/path/to/any/custom/directory/home/user/Desktop/Chromedir --profile-directory="Profile 1" --remote-debugging-port=7878

1. make sure "Profile 1" is already existing in the same --user-data-dir (make sure user Profile 1 has necessary chrome://components/ to run any apps that require those components)
2. you can use any free port in place of 7878 verify that http://localhost:7878 is running and returns value.

This should manually launch chrome with the "Profile 1" profile, and so long as it has logged into the site in question, it will stay logged in like a normal user so long as you follow these instructions to run the tests.

I used this to write a quick netflix bot that clicks the "continue playing" button when it pops up, and it's the only way to get DRM content to play as far as I have found. But it retains the cookies for the login, and also launches chrome with whatever components the profile is set up to have.

I have tried launching chrome with specific profiles before using different methodologies, but this was the only way to really force it to work how I wanted it to.

Edit: There are methods for saving cookie info as well although I don't know how well they work. Check out this link for more info, as my solution is probably not the best solution even if it works.

The API mentions Driver#quit as something to "quit the browser". It seems that adding @driver.quit to your rescue would do what you want.

I do not think selenium-webdriver supports Firefox 19. Try with Firefox 18.

If you can, the best possible thing to do is have a system in which each Selenium test gets it's own data state (ie: DB tables dropped and recreated, bootstrap data re-inserted, and caches cleared). This is easier said than done and usually is only possible if the project planned for it from the start.

The next best thing is to have a consistent DB state for each test suite/run. This is not as nice since there is now a strong chance that some tests will depend on the success of previously run tests, making it more difficult identify true failures vs. false negatives.

The worst case, IMO, is to use a static DB in which each test run mutates the date. This almost always leads to problems and is usually a "project smell". The key to doing it the "right way" (again, IMO) is to be vigilant about any state/schema change and capture it as part of the automated test/build process.

Rails does a good job with this already with Migrations, so take advantage of them! Without knowing your situation, I'd generally question the need to run Selenium tests against a snap of the full DB. Most DBs can (or should) be distilled down to less than 1MB for automated testing, making automated schema migrations and data reset much more efficient.

The only time I've seen a "valid" reason for massive DBs for Selenium tests is when the DB itself contains large chunks of "logic data" in which the data affects the application flow (think: data-driven UI).

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.

I've figured it out. The main problem was the Rakefile and files in the directory to not having the correct path and filename convention used with Minitest.

This Rakefile solved the issue:

require 'rake/testtask'

Rake::TestTask.new(:all) do |t|
  t.libs << "tests"
  t.test_files = FileList['tests/test_*.rb']
  t.verbose = true
end

Rake::TestTask.new(:webpc) do |t|
  t.libs << "tests"
  t.test_files = FileList['tests/test_web_*.rb']
  t.verbose = true
end

task default: :all

There are some possible ways depending on how specific you want the XPath to be, f.e. if you simply want to count child elements of any name, then you can use * :

row.find_elements(:xpath => "*").length

and if you want to specifically count child elements of certain names i.e li and div :

row.find_elements(:xpath => "*[self::li|self::div]").length

Here is the Answer to your Question:

Instead of absolute xpath you can consider constructing logical xpath. Here are the xpath which you can use:

1. Passing the text toys within Search:

   browser.find_element(:xpath,"//input[@name='keyword']").send_key("toys")
   

2. Clicking on Search button:

   browser.find_element(:xpath,"//div[@class='search-icon-tru']").click
   

3. Click on first product:

   browser.find_element(:xpath,"//div[@class='product-item__product-title'] [contains(.,'The Peanut Shell Bella Elephant Plush')]").click
   

Let me know if this Answers your Question.