Critical commentary follows:
[i]I have taken a leap into watir and I must say that at first glance it was
fun, easy and usable. However, when I needed a more complicated and managed
solution it fell flat. Watir provides an easy and simple way to access DOM
elements and complete user (through web UI) tasks. Thus, really great for smoke
test automation.
Sadly though, its support for multiple scripts to be run in a preassigned
sequence is pretty much non-existant. If you do approach your testing from the
perspective that you have one long user process you want to emulate through
scripting, then it can work. If you have more building block orientated
approach, the structure doesnt accomodate that. At all.
I dont see the gains in creating massive and long process action changes
embedded in a script that covers a pieces of functionality. I see it as a
duplication of effort, difficult to maintain, difficult to know what you have
at a glance and, in the end, a maintenance nightmare. I want a better setup
that allows me to do the following:
* Allows me to reference the scripts that I want to run and,
* Allows me to determine the order that they run in
* Gives me better and clear reporting after the tests have finished running
and,
* Gives me that end result in both .xls and .html format
It is severely limiting not to be able to reference scripts. Currently, due to
nature of the DMS it is easy to build shorthand action scripts. Action scripts
cover (at the most basic level) user end to end actions. An example of this
would be Login. All it requires is a username and password and the user must
click on the Login button. I want to be able to self-contain that action
within a script and then call it whenever I want to set up a longer process
chain of actions.
If I can build a better test runner to manager to manage that, I think that
would probably take first place. (and possibly integrate it with a test case
management tool.. something along those lines). Otherwise, the hunt continues
[/i]
http://seryph.wordpress.com/2007/02/12/watir-close-but-not-close-enough/
I quote this because i basically agree. Watir is only a browser driver and we
leave it to users to build their own testing framework using Test::Unit and
Test::Unit Reporter and the like. This in fact is how i spend much of my time
at my day job.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.openqa.org/thread.jspa?threadID=6532&messageID=18618#18618
_______________________________________________
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
