A Smattering of Selenium #63

• Watir to WebDriver: Unit Test Frameworks – Well, its ‘big’ news. Of course, Watir can use WebDriver so they didn’t have to port their scripts to a different API (I sure hope they have the API well abstracted away from their scripts). And of course the title of the post implies that Facebook thinks that Watir/Selenium scripts are ‘Unit’ tests which is suspect at best…
• Selenium tests for Jenkins — Yup; Jenkins now has a set of Se scripts for it. Fork, modify and sent pull requests.
• Thucydides appears to be another full-feature framework built around WebDriver
• NativeDriver and iOS: First Impressions looks to be the first of a series of posts about automating mobile apps
• Managing Locator Builders in Selenium IDE introduces a new feature that we snuck into the most recent version of Se-IDE. Still needs a bit of polish, but we’re getting there.
• The evils of `except:` is a good reminder about naked excepts in your code. Doubly true in automation where you really want to have exceptions bubbling to the top.
• Adding Mozmill tests to the Selenium IDE build system walks you through how to add Mozmill tests to a CI environment. A lot of Se-IDE plugins are really only testable through Mozmill.
• So who is going to buy me a Keep Calm and Continue Testing t-shirt.
• And while we’re at it, who is going to add Se to the Ubuntu Software Center
• This issue’s debate is At Least Three Good Reasons for Testers to Learn to Program vs. At Least 3 Reasons for Software Testers NOT to Learn to Code. Of course, if you are doing Se stuff, that alone is reason to learn to code — automation is programming.