Just one think that I may want to say about the use of Webrecorder. One of the things it does is shows the Ruby code created as you are using the browser. This for changes the nature of the tool.
I used webrecorder to get snips of code when I was unsure. Once I had those I modified them by adding variables and putting them in a loop. For me that is very different from the Seque recorder which (I hope I'm not presumptuous here) was marketed as a replacement for coding rather than an adjunct. Cheers Pierre Garigue -----Original Message----- From: Bret Pettichord [mailto:[EMAIL PROTECTED] Sent: Friday, March 24, 2006 1:50 PM To: [email protected] Subject: Re: [Wtr-general] Watir WebRecorder 0.5 Update [stuff deleted] My suggestion is that you make WebRecorder open source and add unit tests to it. And create a separate mailing list to support these people. I was at Segue when they added a recorder to QA Partner. Originally the people calling for tech support were pretty savvy and they talked to knowledgeable people right away. But with time they had to create a new tier of tech support just to deal with the recorder people. By then i had left Segue, but was still using their tools. It was frustrating for me because when i called in i had to work my way through a layer of staff who knew less about the tool than me, but who were convinced that i was just a stupid user (because 90% of their users were in fact stupid users). Widespread use of recorders for Watir will also force us to create a tiered community. _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
