From: Joel Pearson <lists@...>
Date: 2013-02-04T01:37:02+09:00
Subject: Re: couldn't hit a button using selenium-webdriver

That's not IRB, that's the command console.

One easy way to find out what's going on is to use a webdriver browser 
session created in IRB to navigate to the page, and find out what 
response you get when you manually enter variations on the command. 
without some output it's going to be difficult to trace the issue.

Maybe these would help to give you some ideas:
puts driver.find_elements(:name, "btnEdit").length
puts driver.find_elements(:class, "dk2564").length

Selenium-Webdriver is a bit awkward to use without Watir's API so I 
haven't played with it much. Still, the steps to finding the solution 
are the same: Experiment using IRB, add debugging helpers around the 
problem area by reporting back each line's result, and validate every 
interaction before continuing to the next step.

-- 
Posted via http://www.ruby-forum.com/.