Thanks for sharing Carl's thoughts with us.
I should mention that i have a lot of respect for Carl and the SAFS team. I had detailed meetings with them to learn about open-source projects. It was only after that meeting that decide to commit to what eventually became Watir.
Details from that meeting can be found here:
http://www.pettichord.com/awta5.html
Bret
On 7/13/06,
Adrian Rutter <[EMAIL PROTECTED]> wrote:
Carl Nagle wrote around 12 Jul 2006 on the RRAFS list
You seem to be missing part of the appeal behind the purpose of SAFS and
the original post concerning a WATIR engine. With a WATIR engine we could
be testing our web content with WATIR as a SAFS engine. We could take a
test that originally ran with SAFS for Rational Robot (RRAFS) and run it
with SAFS for WATIR (WAFS?) instead, and vice-versa. We could also use
both and not have to pick just one tool or the other. And when we have to
run the same tests on Linux or Unix the tests could still be portable on
whatever engine we choose to provide there (Selenium, LiveConnect, Common
DOM, etc.).
The idea is to provide test portability, tool-independence, and a common
infrastructure for test development, reporting, and execution regardless of
the tools that will be used. As a SAS example, we would still use the same
test development tools (Excel or Test Composer) regardless of whether we
were using SAFS for Rational Robot (slow) or SAFS for Watir (fast). The
"test data" would be unified because both engines are SAFS engines, and the
reporting would all stem from the same SAFS assets and services.
Your ideas of what could\should be unified or shared is exactly what SAFS
attempts to satisfy--a framework on which any and all of these things can
be attached and shared. Most actually exist already in one form or another
and the mechanisms to add others is present and documented. The issue, of
course, is largely one of time and resources. You or anyone could help
implement a Watir engine for SAFS. Then folks wouldn't have to choose
between writing Watir tests in Ruby or writing portable tests in SAFS.
In any event, thanks for sharing your ideas and furthering this discussion!
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
