+1
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chris McMahon > Sent: November 2, 2005 7:34 AM > To: [email protected] > Subject: Re: [Wtr-general] Architecting WATIR for a WEB application > > > What are some considerations that will help the planning > and layout of > > WATIR architecture if you are to start from scratch to > automate a WEB > > site? I would appreciate hearing from experienced WATIR > users on what > > approaches you have chosen to structure/architect the way you use > > WATIR for your WEB application. Thanks. > > > I suspect that the sophisticated Watir users on this list > would tell you that the answer to your question depends on > individual context. > That is, every project is different. > > As a general principle, though, a lot of people suggest that > your framework should be abstracted from your implementation. > In other > words: start solving problems; refactor; repeat; don't worry > about architecture so much as you worry about solving the immediate > problem-- your architecture will grow as your ability to > solve problems does. As always, I'll cite Kevin Lawrence's > March 2005 Better Software article called "Grow Your Test > Harness Naturally" > which seems to be the most important reference out there for > doing this sort of work. > > -Chris > > _______________________________________________ > 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
