|
As long as there is an option to disable, as was mentioned before,
then this is okay. But I want to make the case very strongly that the
option is necessary. We are doing "screen scrapes", not tests. And in some of our applications, the contents of the pages change dynamically, or based on what input was given on a different page, according to a complex set of rules. In some cases we may not even know in advance what all those rules are. So unlike most testing, we do not know ahead of time what the page contains. Therefore, we make use of this kind of logic a lot: if @ie.<element>(:id, 'id_string').exists? { Do something.} else { Do something else. } end If our applications had to wait for Watir to keep retrying every time an element was not found, our applications could become so bogged down that they would be unusable. From our point of view, the current functionality of "exists?" would be almost completely broken. We would have to re-write applications almost from the ground up. So this is a great idea . . . for some purposes. But if there were no way to disable it, existing code would be broken. Lonny Eachus ==========
|
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
