A Smattering of Selenium #35

(If I wasn’t still recovering from a cold there would be something witty here.)

• We’ll start this week with a cartoon
• So I know I have linked to playing pacman with se 2, but here is a site that explains the ghost behavior. If Google implemented the algorithms properly-ish, then this should be the ticket to crazy high scores. There should be a contest for this…
• Cucumber + Cuke4Duke + Selenium (WebDriver) = Enlightenment is step-by-step instructions for using maven to wire all these things together.
• shell in a box means you can now use Se to automate a unix shell
• How test automation with Selenium or Watir can fail provides two code smells for automation
• UI test smells: if() and for() and files is a bit of a rebuttal with some additional commentary
• Surviving end-to-end-testing… or, using Selenium for fun and profit is a write-up of the XP Day session of the same name
• The first thing that really became obvious to is that the community has to stop thinking about the tools and step back to look at a wider picture of the processes that have evolved over the last decade. Tools are there to assist us with a process, so focusing on tools and not on the process is just causing problems in adoption for new teams. is from Gojko’s article in the December 2010 issue of The Tester. And is extremely important to remember given that this is a tool focused blog
• Missed Øredev? Watch the videos!
• A post from Sauce Labs shows how to put messages in your script runs. Crazy enough, I did something similar.