How to use can_lock method of Selenium.WebDriver Package

Rename:

test/selenium/test1.rb

to:

test/selenium/test1_spec.rb

Is this what you're trying to do? :

def element(element_name, options = {})
  define_method "#{element_name}" do |arg = nil|
    find yield(arg), options
  end     
end

Now define the method:

element(:method_name, visible: 5) {|num| "#csspath#{num}" }

Here yield statement executes the block with a default argument as nil, which will be ''(empty string) while converting it into a string when you call:

method.click #=> will use "#csspath" for find

It will evaluate and use argument if passed like so:

method(1).click #=> will use "#csspath1" instead of "#csspath" for find

  Capybara.register_driver :selenium do |app|
    Capybara.app_host = "http://google.com"
    Selenium::WebDriver::Firefox::Binary.path = ENV['CUSTOM_FF_PATH'] if ENV['CUSTOM_FF_PATH'].present?
    profile = Selenium::WebDriver::Firefox::Profile.new
    profile.assume_untrusted_certificate_issuer = ENV['SKIP_CERT_ISSUER'].present?
    profile['browser.download.dir'] = "#{Rails.root}/tmp/webdriver-downloads"
    profile['browser.download.folderList'] = 2 # implies custom location
    profile['browser.helperApps.neverAsk.saveToDisk'] = "text/csv,application/pdf,application/doc,application/docx,image/jpeg"
    profile.native_events = true
    Capybara::Selenium::Driver.new(app, :browser => :firefox ,:profile => profile)
       #Capybara::Selenium::Driver.new app, :profile => profile
  end

Try with this configuration

Yes it can be used to test Rails. But only from the outside (only through the Browser). So no Unit/Controller/View Tests. You'll need MiniTest or Rspec for those.

My two cents (also see comment by @SteveCarey): Since I prefer to stick with what comes with Rails and use as little external tools as possible:

Have a look at System Tests that have been introduced with Rails 5.1 or, if you are on a older version, see if you can write those tests using Capybara/Integration Tests.

Update:

You can find more details on testing framework here: http://guides.rubyonrails.org/v4.1/testing.html#brief-note-about-minitest

It was Test::Unit and nowadays is Minitest. But the basics are the same so it does not really matter.

Another popular testing framework is RSpec. Which you can use instead of Minitest/TestUnit if you want to. I prefer Minitest but there are pros and cons for both frameworks.

Rails 4.2 came with Unit-tests, Functional/Controller-tests and Integration-tests. The built in thing that resembles Nightwatch the most are Integration-tests: http://guides.rubyonrails.org/v4.1/testing.html#integration-testing

You can also look at libraries such as Capybara (https://github.com/teamcapybara/capybara) which calls itself an Acceptance Test framework. It integrates nicely with TestUnit/Minitest/Rspec.

This is how the Selenium docs () suggest:

require 'rubygems'
require 'selenium-webdriver'

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

element = driver.find_element :name => "q"
element.send_keys "Cheese!"
element.submit

puts "Page title is #{driver.title}"

wait = Selenium::WebDriver::Wait.new(:timeout => 10)
wait.until { driver.title.downcase.start_with? "cheese!" }

puts "Page title is #{driver.title}"
driver.quit

If that is not an option you can try the suggestion from this SO post though it would require some Javascript on top of the Ruby/Rails.

It seems that wait.until is being/has been phased out. The new suggested process it to look for the page to have an element you know will be there:

expect(page).to have_selector '#main_div_id'

So the answer I think is what Andrey Botalov said.

In my case the problem is that I installed a viral software called Conduit. While posing as legitimate software, it is nearly impossible to remove without some sort of anti-virus.

What was happening is in each instance of lauching chromedriver to run a test, conduit would load NewTabAPI.js onto the new chromdriver. This in turn launched a crappy toolbar. In my case InternetHelper1.5.

At the time of kill NewTabAPI.js had multiple copies sitting in the \Users[user]\AppData\Local\Temp\scoped_directory_....

Removing these killed the virus, but I found a number of conduit directories sitting about that I felt prudent to remove as well.

Anyway, that's what I needed to do in my case. In most cases Andrey's comment should do just fine and answers my question.

Based on the Ruby bindings page, the capabilities are set like:

caps = Selenium::WebDriver::Remote::Capabilities.internet_explorer
caps["requireWindowFocus"] = true

Capybara::Selenium::Driver.new(app, :browser => :internet_explorer, :desired_capabilities => caps)

What you're asking is possible using JS, however then you're not really testing the site (assuming you're testing and not just scraping). To do it via JS with Capybara 3.2+ you could do

page.find("#ctl00_ContentPlaceHolder1_as1_divDateRange").execute_script("this.classList.add('open');")

Prior to 3.2 you would need to do something like

el = page.find("#ctl00_ContentPlaceHolder1_as1_divDateRange")
page.execute_script("arguments[0].classList.add('open');", el)

That being said, there are plenty of ways to click the <a> even if it doesn't have any usable attributes (assuming it has size on the page) by scoping to it

page.find("#ctl00_ContentPlaceHolder1_as1_divDateRange > .header > a").click

Instead of modifying the firefox launcher.rb I think you are better off incorporating some logic at each of your scripts. Something like this might help!

Have a look at the link below: Ruby - check if a port is open