[Wtr-general] Switching from Segue's SilkTest to WATIR?

[Tuyet Cong-Ton-Nu]

I am wondering if anyone out there is in the process or has already switched from Segue’s SilkTest to WATIR. Any feedback on how the process went or is going for you would be appreciated? We have adopted Segue’s SilkTest to automate our Web application a few years ago, but we are not happy with how unreliable, hard to maintain, and slow it has performed. After the demo I gave this morning, we want to pursue investing more time in WATIR. So, first of all, thanks for all your help!  You are a great community!   Any feedback on SilkTest to WATIR conversion is appreciated.   By the way here are some benchmark stats that are interesting to know. We picked 2 scripts “Import” and “Analysis/Positions” and coded the exact steps for both WATIR and SilkTest. We ran the scripts about 15 times each in both WATIR and SilkTest and here are the results:   Import script Watir SilkTest Lines of Codes   60 lines of code 200+   Elapsed Time (average of 15 runs)   25 seconds 60 seconds Reliability     No failure when ran 15 times in a row 87% with 15 runs Maintainability   All changes are readily “seen” via View Source or getHTML command.  Compare files can be done and changes can easily be made. Changes in B1 code require updates to the page declarations. This can take between 10 and 30 minutes.     Analysis/Positions  script Watir SilkTest Lines of Codes   105 lines of code 250+ Elapsed Time (average of 15 runs)   52 seconds 120 seconds Reliability    No failure when ran 15 times in a row 80% with 15 runs Maintainability   All changes are readily “seen” via View Source or getHTML command.  Compare files can be done and changes can easily be made. Changes in B1 code require updates to the page declarations. This can take between 10 and 30 minutes.

_______________________________________________
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general