[Wtr-general] packages for two controllers on RubyForge

[Jonathan Kohl]

I was just wondering about having a separate package for the controller Paul
wrote on the Rubyforge site. Chris' iec seems to be geared more for
developers while the one Paul has been working on is more for testers.

I've been using the controller Paul wrote, and have added a couple of
methods for my own use. Paul is getting close to having most of the
requirements I outlined on the WTR site for web testing. 
Here is the status so far:
* hyperlinks - can click links by the text name between the <a href=""> and
</a>
* images - can click images based on the name of the image (this needs some
work, but it does the job)
* buttons - done
* check boxes - done but needs a little polishing
* select items in:
	* drop-down boxes - done
	* radio lists - done
* enter text in text fields - done 
* handle popup warning or error message boxes - Paul is working on this
* handle pages that use frames - Paul has a solution; I haven't tried it yet

* read and handle inline messages - easy to handle with Ruby, but no
generic verification method 
* verify that objects, widgets or text exists - simple enough to do with
Ruby, but no generic method yet. It would be nice to do something like
SilkTest's "exists"


I'm using this controller to automate web application functionality in my
current role as a software tester. Paul and I were talking about using CVS
for his controller, and the Rubyforge site would work well. Currently, we've
been emailing or IM'ing code. It would be good to start using some change
control on his controller.

Does having two packages seem reasonable?

Thanks;

-Jonathan