How to use dismiss method of Selenium.WebDriver Package

I got this working under Rails2 by doing the following (but Rails3 shouldn't be too different):

add the following lines to the top of your config/environments/development.rb:

require 'simplecov'

# clean the existing coverage directory before writing the new results.
Dir.foreach("coverage") do |file|
  next if [".",".."].include?(file)
  FileUtils.rm_rf(File.join("coverage",file), :verbose=>true)
end

SimpleCov.start 'rails' do
  add_filter "/vendor/"
end

Now, go and add a handy controller method to one of your controllers (I added it to an admin controller so I know it won't be accidentally called, but anything will do since you are guarding it for development only use):

class Admin::DebugController < ApplicationController

  if RAILS_ENV=="development"
    # see config/environments/development.rb
    def coverage
      SimpleCov.result.format!
      render :text => "Wrote results. STOP AND RESTART THE SERVER TO BEGIN A NEW COVERAGE RUN!!"
    end
  end

end

Now, start your rails server normally and let your external test suite run against it (or your manual integration QE tester ;)

When you are finished running through your integration tests, hit the url you setup in the admin controller, e.g.

http://localhost:3000/admin/debug/coverage

NOTE: this url only works/exists in development!

Voila! The coverage report will be written out to coverage/** in your rails directory. You can view it by loading coverage/index.html in your browser.

Justification

While the normal usage of SimpleCov is meant for unit and functional testing, adding the ability to evaluate external integration tests gives QE testers valuable feedback about what their testing strategies actually test within the target rails application.

This may be a trivial distinction for the majority of Rails applications, however it is useful when the application operates as a "pass-thru" for a large amount of data from other applications that is dynamically mixed into the application models (for example, a dashboard or console app). In these kinds of apps, rails testers may think they are testing permutations of the app, when in fact they are testing permutations of the underlying data (e.g. a network cluster). In this situation, code coverage gives an additional level of visibility into what is being tested.

Similar to type method I need to focus the Ferrum::Node instance before clicking it.

- browser.at_css('input[name=searchButton]').click
+ browser.at_css('input[name=searchButton]').focus.click

I've never actually tried using selenium-webdriver in a standalone script like that, but I have run into the same problem using selenium-webdriver within the context of capybara/cucumber.

Looking at the source code for capybara, I found this hook which explicitly closes the browser after your script is finished. If you're not using selenium-webdriver with capybara, then this might not be helpful, but it was helpful for me...

gems/capybara-1.1.1/lib/capybara/selenium/driver.rb registers an at_exit hook, which then calls quit on the browser object:

require 'selenium-webdriver'

class Capybara::Selenium::Driver < Capybara::Driver::Base
  ...

  def browser
    unless @browser
      @browser = Selenium::WebDriver.for(options[:browser], options.reject { |key,val| SPECIAL_OPTIONS.include?(key) })

      main = Process.pid
      at_exit do
        # Store the exit status of the test run since it goes away after calling the at_exit proc...
        @exit_status = $!.status if $!.is_a?(SystemExit)
        quit if Process.pid == main
        exit @exit_status if @exit_status # Force exit with stored status
      end
    end
    @browser
  end

You should be able to monkey-patch the quit method so that it does nothing, like so:

  Selenium::WebDriver::Driver.class_eval do
    def quit
      #STDOUT.puts "#{self.class}#quit: no-op"
    end
  end

Note: If you are using Selenium::WebDriver.for :chrome and chromedriver -- which you aren't, but other people might be -- I noticed that it also kills the chromedriver process, and as soon as that "service" process is killed, the Chrome browser process that was connected to it also quits.

So I had to also prevent that service process from stopping, like so:

    Selenium::WebDriver::Chrome::Service.class_eval do
      def stop
        #STDOUT.puts "#{self.class}#stop: no-op"
      end
    end

There was one other problem I ran into, which probably won't affect you, unless you're using this driver with cucumber... Even after I got it to leave the browser open, it would be left open on the "about:blank" page. It looks like this is triggered by this hook:

gems/capybara-1.1.1/lib/capybara/cucumber.rb:

After do
  Capybara.reset_sessions!
end

Which calls gems/capybara-1.1.1/lib/capybara/session.rb:70:in `reset!'"

Which calls gems/capybara-1.1.1/lib/capybara/selenium/driver.rb:80:in `reset!'":

  def reset!
    ...
    @browser.navigate.to('about:blank')
    ...
  end

And I solved that with another monkey-patch:

  Capybara::Selenium::Driver.class_eval do
    def reset!
    end
  end

So, in this particular example, you could do

@driver.find_elements(:xpath, "//div[@class='currency_dropdown']/div[@id='scroll-innerBox-1']/div[not(@style='display: none;')]").size

This should return 1 when USD is typed into the search field.

Edit: I recommend getting ChroPath for your preferred browser (FF or Chrome). It helps significantly when testing xpath.

After entering the search term, you can get the value (e.g. element['value']) from the text field, and use an rspec expectation to validate that the correct string has been entered. For example:

#foo_spec.rb

require 'selenium-webdriver'
require 'rspec'

describe "Contrived Example" do

  it "enters a search term" do

    driver = Selenium::WebDriver.for :firefox
    driver.navigate.to "http://google.com"

    element = driver.find_element(:name, 'q')
    element.send_keys "test string"
    sleep 1
    expect(element['value']).to eq "test string"
    driver.quit

  end

end

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

The issue is that you need Watir 7 to work with Selenium 4. Please upgrade to the latest version of Watir and it will work.

You can use following xpath for your case:

driver.findElement(By.xpath("//*[contains(text(),'Verify Now')]")).click();

Hope it will help you.

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

# in test group
gem 'selenium-webdriver'

Then run bundle install