On 2/9/06, Brian Vallelunga <[EMAIL PROTECTED]> wrote: > As I was typing in line 261 of very basic and repetitive Watir code, I > that much of this scripting should be able to be done declaratively, > especially when using the scripts to simply input values and check > responses. Has anyone done anything like this?
I currently use a little homebrew framework like this. I just have a big batch of XML files that contain elements like <button name="name" method="click" /> and so forth, contained inside <step> elements, and a driver script that parses the XML files and turns the contents into Watir statements. For complex cases that require more code (like popup handling) I just make special tags whose name correspond to methods that contain the special case code. However, I'm strongly considering a change, using Test::Unit instead of continuing with my own stuff. This is because I'm trying to figure out the best way to hand over the framework to the dev team to use, and my module for handling my XML files feels kind of kludgey. I also don't want people to have to discover limitations with my XML format and have to hack on that to handle new cases. Also, using a standard unit testing format rather than something I threw together will probably be more appealing to the dev staff where I work. :) On the other hand, not using the XML config files will probably make for a steeper learning curve. The tradeoffs are interesting. There's also WET (http://wet.qantom.org/overview.html) which I haven't looked at in depth, but might be applicable for what you want. Thanks Bill _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
