On Oct 25, 5:22 am, Željko Filipin <[email protected]> wrote: > On Tue, Oct 25, 2011 at 2:18 PM, Cliff Cyphers <[email protected]> > wrote: > > > New project as this is completely different from the minitest approach. > > This is a replacement for qa robusta, or do you plan to further develop > both? > > Željko
I think I sense another watir podcast opportunity. Cliff, what you have provided is good info, but might be a little bit towards the deep end of the pool for testers who are just learning to script with Watir and get a bit out of their depth once you start talking about classes, and close to complete confusion once you start talking about 'modules' I think it might be handy to have an outline at a fairly high level of things like 'what goes where' and how the pieces fit together. That's all second nature to you since you designed the framework, and it might not be that hard for someone who has worked with one or two other frameworks to grasp, but for the beginner it's just sort of overwhelming and hard to know how and where to start. I'd like to see a lot more people make use of some of the great work that's being done on frameworks to allow effective testing with watir, and integration with other tools like rspec, cucumber, minitest, etc. Most experienced folks know that these things are the path to effective automation that can scale and grow and not become UN- manageable. Being able to leverage things like existing reporting tools etc also prevents you from having to reinvent a lot of wheels that are already out there. However one of the very strengths of watir (that you can dive in with almost zero prior programming/ scripting experience) also tends to create a steep learning curve and barrier to entry when it comes to choosing or adopting a framework. -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
