On Sun, 9 Oct 2005, Jason R Huggins wrote: [...] > Anyway, I think we should use the same terms used by the SOAP and REST > guys --- Document vs RPC. [...] > So we have: > 1) Document Literal Selenium > and > 2) RPC Selenium
+0, iff buzzword compliance is in the requirements <0.5 wink> > Document Literal Selenium can have several "encodings": > 1) HTML table > 2) JavaScript + HTML table > 3) Wiki table > 4) "twill style" (see--> > http://www.idyll.org/~t/www-tools/twill.html#what-is-twill) > > (Only encoding #1 is currently supported, but I'd like to support 2,3,4 > someday) [...] Those are not different encodings of the same data. For example, 2) cannot be encoded as 1). I'm +0 on the fancy names: 'HTML Tables mode' describes what I'm personally interested in describing: the current HTML tables mode. The other ways of writing functional tests that you enumerate above (1,2,3,4) might be useful, but they're new stuff, not just different encodings of what can currently be done with FIT-style HTML tables as they exist now (at least, 2 and 4 are -- not sure exactly what you mean by "wiki table"). John _______________________________________________ Selenium-devel mailing list [email protected] http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
