The other difference is you won't normally be dealing with an application that actively TRIES to be difficult to script against.
Now truthfully I can't say for sure that is the case (having not talked with anyone at google who can confirm that suspicion) but sure as heck both FEELS like it IS the case, and also makes sense from a standpoint that most people who would want to be automating the google UI would do so for 'evil' (e.g. sending spam) purposes, and that's something google would seek to prevent. On Aug 11, 1:30 am, Željko Filipin <zeljko.fili...@wa-research.ch> wrote: > On Wed, Aug 11, 2010 at 7:21 AM, Sharma Vishav <sharma.vis...@gmail.com> > wrote: > > > My main aim here is to get knowledge on how to effectively use watir > > in web application which present you such situations. > > The main difference in testing Gmail just for fun (by the way, just today > they completely changed it) and testing an application (and get money for > it) is that in the second case you usually have access to developers and you > can ask them how to access and element, or ask them to make a change so the > application is more testable. > > Željko -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. You received this message because you are subscribed to http://groups.google.com/group/watir-general To post: watir-general@googlegroups.com To unsubscribe: watir-general+unsubscr...@googlegroups.com
