Good afternoon:
We created a testing suite using test environment A. Various strategic
sleeps were put in place to optimize the execution of WATIR scripts against
this test environment. For the most part these test suites execute with
some reliability.
On Friday I attempted to run the same set of scripts on my development
environment. Of course the scripts would break (primarily failed
assertions) because my laptop is not as powerful as the testing machines.
How do y'all handle the issue of pointing your tests to different
environments and not having the scripts execute with reliability?
Should we create scripts in the worst case environment and assume they will
function on the production ready hardware?
I believe the primary problem is the latency associated with Pop ups. Does
anyone use any tricks to make their scripts more reliable?
Despite everyone's hard work on WATIR, I am finding this to be an extreme
limitation and I am once again questioning my choice of WATIR as our
preferred testing solutions.
Will any of the new activities for the next release address this concern?
Am I isolated in having this concern?
Any thoughts or suggestions would be appreciated.
Thanks,
Carl
--
"NOTICE: The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential. If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected."
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
