My last post started with this title, but since the exposition at the start started to get long, I broke it off. So here’s the rest, in a significantly sillier vein:
Watir is written in Ruby, and everyone except Matz discovered Ruby because of a Danish graphic designer named Why, commonly known by his street name ‘Rails’ (or DHH for short — it’s the Danish abbreviation for something vulgar.) Rails didn’t invent code generation, but he made it cool again. He also made DSL more popular than Cable, but I don’t know Why personally.
Anyway, I found a couple (ok, several) interesting page-based frameworks for watir, designed to make testing easier.
The first one is called watirloo, after a famous aquatic fun center discovered by a time-travelling midget originally from 1988. His relation to Michael J. Fox (of the Rails comic strip) is uncertain. Now watirloo seems like a nice framework, but I can’t get over the choice of names for some of the objects. While sticks and stones may not smell as sweet as a rose by any other name, I have no intention of spraying anything all over my face.
The next is called taza, named for it’s infamous pythonic sidekick, who is in fact a monkey, not a snake. It uses the common script/generate formula so dear to the hearts of Rubistas everywhere.
The two hundred twenty-five pound chimpanzee hanging around the watir cooler is Cucumber, but only kooks would like it because it’s based on rspec, which while a nice idea, you wouldn’t want to use it for testing (or marmalade), because it’s not that fun.
And so I lied, that’s five frameworks, and I didn’t even give any useful information on either. Since my two reader (hi mom & dad) prefer selenium to watir (it goes down smoother), I’ll mention one other: tellurium, which I think actually tries to assist in the building of those page objects via the IDE.