Hi Charley, I might need to talk to you. As I've been learning Watir, I steered away from established frameworks (frankly, out of my lack of understanding) and developed my own framework which included HTML reporting. However, as the number of tests have been increasing and gaining more visibility to others within my team, I'm finding that it's become more difficult to maintain.
So, I might need to (gulp) re-structure my tests. I still need to talk to my boss about this, but I'll take a look at those links and develop some simple tests. Hopefully, this will inspire me to adhere to already-established frameworks. -George On Nov 15, 1:34 pm, Charley Baker <[email protected]> wrote: > This might help some of you and definitely worth checking out > :http://www.cheezyworld.com/ He has a couple of pages now on cucumber > and browser testing, developing a page based framework. > Tazahttps://github.com/scudco/tazais a framework I've architected and > used in several large companies, which has many of the same concepts > that people are moving towards - e.g. page and site models. Please do > check these out, use them and try not to reinvent your own framework. > > Ruby has builtin support for a base test library - a few of us have > added additional test frameworks on top of that which are used in > heavy large scale application testing with AJAX and all the goodness > from years of experience. Cheezy's posts are a build up of real life > experience using Watir and Cucumber on various client sites. I'd > highly recommend following them, there are several more coming. > > I'll drop a hint, Taza is an awesome framework for web ui testing, > well used and also extensible. If you want to get involved in either > Taza or Watir, we've got a lot of work to do, and I'm happy to mentor > from the newbie on up. > > Cheers, > > Charley -- 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]
