//
AboutWtr


Web Testing with Ruby is a burgeoning group of geeks seeking to improve on the state of web testing tools with help of Ruby (see WhatDistinguishesUs).

In October 2001, ChrisMorris started assembling some Ruby code in an open source lib called ClIEController to automate Internet Explorer via its COM interfaces. It wasn't much, but it was a handy assistant for the things it handled. [see ClIEController/HiStory for the arcane nitty-gritty]

Some time after that, with a little bit of Chris's code and some inspiration from Brian Marick and BretPettichord, PaulRogers started efforts on his job to use Ruby to test IE. He and other staff at DigitalOilField have since developed an impressive library of code and Paul is currently seeking to get it open sourced, but it doesn't look like that's going to happen.

In September 2003, Chris got sucked into a mail thread with Brian, Bret, Paul and JonathanKohl where someone wished for a Wiki or somesuch to serve as a home base for this effort. Chris ponied up some wiki space and if we're still here ... here we are.

In August 2004, Bret posted an announcement about a new direction/addition to the WTR project, called WATIR (see WaTiR):
The Plan for WATIR

The Agile XP Universe conference in Calgary this week provided an opportunity for us to get our approach reviewed (we taught a tutorial) and have face-to-face discussions for the first time. We’ve developed plans to develop a new tool, which we are calling WATIR (Web Application Testing in Ruby). Looking at the existing tools in the WTR as spikes, we plan to build a tool from scratch using test-driven development, reusing code from WTR [IeC], and building on the unit testing techniques developed in the Scripting101 material. This tool will have 100% coverage by unit tests.

We have sketched out the API to the tool and have secured support from managment at both Wireless Matrix and ThoughtWorks for our participation in this project.

Our initial goal is to build a tool sufficient to support the Scripting101 tutorial. This entails support for buttons, text fields, check boxes and forms, accessing them by name, action or value. Next will be supporting WRX’s needs, entailing adding support for radio lists, frames, links, and selection lists. We’ll also be adding a logging interface, including selectable output to the console or xml suitable for cruise control.

September and October 2004 have brought on a new set of code commits from Paul Rogers with the WaTiR codebase.

| Email | Reload ? || Find | Recent | Home last update: Sun May 29 2005 08:00 AM