How to use with_timeout method of Selenium.WebDriver Package

The easiest way to deal with that is to use Poltergeists blacklist to block the url - https://github.com/teampoltergeist/poltergeist#customization - and/or - https://github.com/teampoltergeist/poltergeist#url-blacklisting--whitelisting

If your situation is more dynamic you could rescue the exception, parse out the URL, add it to the blacklist, and then retry the visit.

Additionally, there is no need to override needs_server?. If you don't pass a second parameter (the app to run) to Session#new (which you aren't doing) then needs_server? is irrelevant.

I have found the problem there is no auto discovery for nodes, this fixes it:

java -jar selenium-server-standalone-2.3.0.jar -role webdriver -hub 192.168.10.52:4444/grid/register port 5555 -browser browserName="internet explorer",version=8,platform=WINDOWS

gem install nokogiri

You can do the same with the other gems.

try it this way

element = browser.find_element(:xpath => "//*[@id=\"tabpage_1\"]/a")

Note: Escape the double quotes.

Tip - If you use a nice text editor (example - Sublime), the colour of the text will change and will help uou detect errors like these

selected? should be working for Options, checkboxes, and radio buttons. But a safer method could be to look at the checked property yourself:

element.attribute("checked") #false
element.click
element.attribute("checked") #true

As for why selected? isn't working, is the box appearing checked after the WebDriver clicked? I would assume you have some JavaScript interfering with your actual click, or perhaps you're handling the wrong object on accident. Judging by the xPath you're using, it's possible you accidentally found the wrong object.

Create a script file with the below content and include this on top of every page before any other JS that logs to console:

(function(old)
{
   console.log = function(str){  
                    //save the str in a hidden field on page
                    old.call(console,str);          
                 }

})(console.log);

The hidden field will have all the log data which can be posted back to server. Same can be done for other console methods like error etc

Assuming the button you're referring to is actually a button (<button> element, or <input> element with type submit, reset, image, or button) then Capybaras :button selector will (by default) wait for it to be non-disabled.

click_button('Something')

or

find_button('button_id').click

or

find(:button, 'button_value').click

If any of the finder or action methods aren't waiting long enough for a specific element you can always increase the maximum wait time for a specific finder/action by passing a :wait option

find(:button, 'Something', wait: 10).click

If you're not using selector types (if not, why not) and instead are just using raw CSS to locate the element then you can use the :enabled pseudo class along with your existing CSS and something like

find('#my_button:enabled', wait: 10).click

If the element you're calling a button isn't actually a button but some other type of element (<a> etc) styled to look like a button, then you'll need to explain exactly how you're disabling the "button".

99% of the time if you need wait_for_ajax you're doing something wrong. In your current case you should just be doing

expect(page).to have_no_css('.k-loading-color')

which will wait up to Capybara.default_max_wait_time seconds for matching elements to disappear. If you need to allow longer than you have Capybara.default_max_wait_time set to you can override the maximum wait time like

expect(page).to have_no_css('.k-loading-color', wait: 10)

which will wait up to 10 seconds for any matching items to disappear

Capybara 2.5.0 is also ancient, being that it was released August 26, 2015. I would recommend upgrading to the latest release (2.12.1 as of now).

within will wait up to Capybara.default_max_wait_time seconds for a matching visible element to be found, and if not found will then raise an exception. If you're saying it takes 10 minutes to do that then you need to reduce whatever you have set Capybara.default_max_wait_time to.