Another interesting point came to my mind right now. In my (previous) company, we had created Ruby scripts for functionality testing of the websites using the Web Automation Testing in Ruby techniue. And, as another big sory was coded and was ready for testing, we would just add another block of code in our master script.
Will you say it was following an agile testing methodology? Do you cover web-testing in your book?
Ruby can be very powerful as a testing tool. But like any code, it can get out of hand very quickly. I suggest you practice good OO coding methods by extracting common libraries and methods.
It is important to add tests for each new story, but don't forget to maintain your tests. Technical debt (bad coding habits) can sneak up on tests tool. We do cover automation test strategies at a high level in the book, but don't go into detail. Web testing is not covered specifically, but many examples are based on web applications.
Co-author, with Lisa Crispin: Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley, 2009) www.janetgregory.ca