> Well...
> > (1) There should be documentation that specifically
> states how to drive a Javascript -- as in, use
> .link(:url, "path")
> > (2) It should point out that it is driven by
> "click", not fire_event('onclick').
> > (3) Actually, there should be documentation that
> identifies all of the available API's, and provide
> examples for each. Right now the Watir User Guide is
> too simple. It doesn't handle real world situations.
> >   
> I believe most of this is documented in the API
> Documentation.
> http://wtr.rubyforge.org/rdoc/index.html

OK, not to be negative, but surely you're joking.
Have you looked at that page? It is completely bassackwards when you are trying 
to find something. It is organized top down, hierarchically, and has no search 
feature.

So...if I want to go to the rightmost list and look at each and every 
method...some are well documented others not so documented.

But let's take this example: 
ie.frame("top_frame").link(:url,"javascript:Events.invokeEvent(\'2_11_act\')").click
Now, the rdoc for frame says:
===
Typical usage:

  ie.frame(:index, 1)
  ie.frame(:name , 'main_frame')
  ie.frame('main_frame')
===
Good enough. But does it say I can do ie.frame("top_frame").link? No. Is "link 
listed as a Method? Why yes it is...if I knew that method was what was required 
here, that would be useful -- but since in the code, the Javascript is not 
associated with an HREF, it is not obvious that I need a link -- or even that 
there is a method called link. So I have to scroll through all methods hunting 
and checking. And even then -- I have to take a big guess because the typical 
usage says:
===
Typical Usage

  ie.link(:url, /login/)              # access the first link whose url matches 
login. We can use a string in place of the regular expression
                                      # but the complete path must be used, 
ie.link(:url, 'http://myserver.com/my_path/login.asp')
  ie.link(:index,2)                   # access the second link on the page
  ie.link(:title , "Picture")         # access a link using the tool tip
  ie.link(:text, 'Click Me')          # access the link that has Click Me as 
its text
  ie.link(:afterText, 'Click->')      # access the link that immediately 
follows the text Click->
===
See? Nothing about Javascript in there. Which there should be -- since this is 
a pretty common Javascript situation I think. So even if there WAS a search 
feature -- it wouldn't have hit on this. So as I result I basically wade 
through the forum, trying this and that.

Look, I am not complaining about the work that has been done -- a number of 
people have done an excellent job with Watir. What I am saying is that if 
Testers are to use Watir, some much better documentation needs to be developed. 
As it happens, I am working up documentation as I go through this and learn 
Watir, and eventually that may be of use, but...it doesn't help me now! ;-)
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.openqa.org/thread.jspa?threadID=4171&messageID=11912#11912
_______________________________________________
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general

Reply via email to