How to use handler method of Selenium.WebDriver.SpecSupport Package

The answer of Ben did not work for me, I had to adjust it to the following:

driver = Selenium::WebDriver.for :chrome

bridge = driver.instance_variable_get(:@bridge)
service = bridge.instance_variable_get(:@service)
process = service.instance_variable_get(:@process)
process.pid
# => 22656

I think the error log is self-explanatory. Going forward IEDriver has to be downloaded separately, as you might be doing for chromedriver till now. A good explanation by the creator here . You can download the driver zip from the link in the error log and add it to your PATH. Read more @ IEDriver

If you have rspec-expectations, could you use:

expect(response_headers['X-Frame-Options']).to include('Deny')

As a guideline, assertions should be done in tests and not in page objects. Of course, there are times when this isn't a pragmatic approach, but those times are infrequent enough for the above guideline to be right. Here are the reasons why I dislike having assertions in page objects:

1. It is quite frustrating to read a test that just calls verify methods where assertions are buried elsewhere in page objects. Where possible, it should be obvious what a test is asserting; this is best achieved when assertions are directly in a test. By hiding the assertions somewhere outside of a test, the intent of the test is not so clear.

2. Assertions in browser tests can be expensive - they can really slow your tests down. When you have hundreds or thousands of tests, minutes/hours can be added to your test execution time; this is A Bad Thing. If you move the assertions to just the tests that care about those particular assertions you'll find that you'll have much quicker tests and you will still catch the relevant defects. The question included the following:

   Putting verification code in page methods multiplies the power of automation by allow you to get a lot of verification "for free"

   Well, "Freedom Isn't Free" :) What you're actually multiplying is your test execution time.

3. Having assertions all over the place violates another good guideline; "One Assertion Per Test" ( http://blog.jayfields.com/2007/06/testing-one-assertion-per-test.html ). I don't stick religiously to it, but I try to follow the principle. Where possible, a test should be interested in one thing only.

4. The value of tests is reduced because one bug will cause loads of tests to fail thus preventing them from testing what they should be testing.

   For example, let's imagine that when you login to your AUT, some text appears that says "logged in as USER". It's appropriate to have a single test validate this specifically, but why wouldn't you want to verify it every time login is called?

   If you have the assertion in the page object class and the expected text changes, all tests that log in will fail. If instead the assertion is in the test then only one test will fail - the one that specifically tests for the correct message - leaving all the other tests to continue running to find other bugs. You don't need 5,000 tests to tell you that the login message is wrong; 1 test will do ;)

5. Having a class do more than one thing violates 'S' in SOLID, ie: 'Single Responsibility Principle' (SRP). A class should be responsible for one thing, and one thing only. In this instance a page-object class should be responsible for modelling a page (or section thereof) and nothing more. If it does any more than that (eg: including assertions) then you're violating SRP.

Not positive, but I think the update to Firefox 14.0.1 might've broken it. Our tests just broke too. I'm still working on a fix.

UPDATE: Yeah, I downgraded to Firefox 13.0.1 and my tests are working now.

You can get the version of a gem from the source_location of a method of one of its classes. For example:

Selenium::WebDriver.method(:for).source_location.first[/selenium-webdriver-\d+(?:\.\d+)*/]
=> "selenium-webdriver-2.53.0"

I always execute my specs.rb from the folder "specs"

Don't.

Run your specs from the root folder, i.e. one level above.

Your command should be:

# (To run just the one file)
rspec specs\spec.rb

# (To run the full suite)
rspec

Side-note: Don't go against the conventions by naming the file spec1.rb. All test files should be named like: <something>_spec.rb; any other files should be used for helper methods etc.

I have seen this happen in my own tests, but on an intermittent basis, and never completely reproducible. What seems to happen is that Selenium WebDriver just becomes blocked and unresponsive.

I know that I have just had to resort to rescuing the error, logging, and retrying in my code. After a few retrys, Selenium WebDriver seems to become responsive again and I'm able to continue on in my tests from there.

I have contacted the maintainer of the Ruby WebDriver gem, and he needs a reproducible test to be able to do some solid debugging. If you are able to provide a reproducible test case, please share it with us so that we can look into this issue. You can use this gist as a starting point to share with the community.

You have selenium-webdriver-3.0.0.beta3.1 which is only for Firefox 48 and later (and not yet properly working). Fallback to selenium-webdriver version 2.53.4 and try again.

And also try this..

• In the terminal change directory path to the directory where gem was installed
• Run gem uninstall selenium-webdriver
• Run gem install selenium-webdriver -v 2.53.4