Brett wrote :'Many of the commercial tools have suffered from the fact that key
design decisions were often made by developers with naive views oftesting. I don't want Watir to suffer the same fate'> >Besides the shrink wrapped test tools we all know, another good example of the way developers see automated testing concepts is in :Effective GUI Testing Automation : Developing an Automated GUI Testing Tool
by Kanglin Li, Mengqi Wu(they have another book that is on auto-testing the middle layer of .Net apps using reflection, without a gui)The idea there is to get to the point where you can click one button and the automated test focuses on testing advertised properties and methods of the AUT, but more at the component and widget levels, not at the functional requirement or use case level. I am not sure if this is naive, or just the way most developers see testing - as doing it from the ground up, not down from the requirements.- Mike Tierney
I think that this is a very interesting book and certainly don't put it in the "naive" category.
At the very least, unlike the commercial tools which hide their algorithms, Li & Wu put everything out in the open. They also put testability first.
Bret
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
