In WTANZ 07, Oliver helped us install Ruby and Watir (it was rather painless). After the install, we were to log into the Weekend Testing web-site and add a forum post. Since that session, I’ve been playing with Watir at work and discovered that the Firefox extension, Firebug, together with the information in the Watir google group greatly speeds up the learning curve for writing tests.
This week, on Sunday (for most ;o), we will be writing automated tests of the Weekend Testing web-site with Ruby, Watir and Firebug.
The mission is to find a bug in the Weekend Testing web-site and write a failing Watir test for that bug.
There are 4 learning objectives:
- Learning the structure of the Weekend Testing pages through the use of Firebug
- Improve our Watir syntax using the Watir google group
- Find out which bugs lend themselves to being recorded in an automated test
- Shed some light on the utility of writing failing tests for a bug that’s been found. Is it a useful way to record what happened or is there too much overhead involved? I’ve heard both sides and would like to investigate this for myself.
Note: This session will be better for everyone involved if we all have watir, ruby, firefox and firebug installed. If you want to participate but don’t have them installed, please check out the transcript from WTANZ 7. Everyone in that session had watir working by the end.
If you’d like to participate, send an email with your skype id to weekendtestinganz at g m a i l dot com
Times:
Sunday, August 21
Sydney 4:30 pm
Wellington 6:30 pm
Manila 2:30 pm
Frankfurt 8:30 am
Bangalore 12:00 pm
Seattle, Saturday 11:30 pm
Update: Here is the transcript from our session. Life has kept me from writing a complete follow-up (or anything else), but I am hopeful Life will cut me some slack in the next week.
Are you going to do a follow up on how this day went. Id love to know.