It's probably too obvious to mention, but since I am the master of all
things obvious, I will: let's make sure that every driver conforms to
as much as the Watir API as is reasonable. Ultimately, if we can have
more than one driver then we should be able to use the same Watir
scripts regardless of which browser/OS we're on.
It may be that the Watir tests should be packaged as a configurable set of tests that could be used with any of the Watir-Browser projects. Each test would be tagged to indicate which browser suites it is included in. This feature could even be used with Watir/IE -- in that we have some tests that will work with IE in background mode and others that require it be in the foreground.
But the bigger issue of ensuring compatability between versions of Watir is tricky. For example, FireWatir doesn't support frames. Is this reasonable?
Fit has something called FAT which are the tests that a Fit implementation is expected to meet. I think there may be a 1.0 and 1.1 version of these. We'd have to do something similar for MultiWatir.
And even then, i suspect that each implementation would have some additional features that were not part of the standard API. For example, Watir gives direct access to the ole object, but any tests that make use of these won't be portable. This suggests that each implementation also should have a "strict" mode where it only allows execution against the core API or least creates warnings for all other uses. This way, users (or their managers) could make sure their tests were portable. Otherwise they wouldn't know until they tried.
Bret
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
