A Smattering of Selenium #80

I should have learned not to boast about getting caught up with links.

• Automating BrowserID with Selenium is pretty awesome. (As is BrowserID.) Now if this was only installable via pip or easy_install…
• Ruby Trick Shots – heed the disclaimer; not an exercise in Ruby best practices
• Keep It Functional – iPhone Test Automation talks about another automation framework for mobile. At some point Selenium is going to grow Objective-C bindings I fear.
• Requests for Python is fantastic. Requests for PHP looks to be equally so. (I suspect my php webdriver bindings are about to become a much larger fork of the Facebook ones.)
• Is Test Automation a “Project”? – hint: it’s not.
• Keeping Selenium Tests 100% Blue is a video of January’s SFSE. And Selenium Meetup West Coast Style is a rebuttal.
• Selenium’s Sweet Spot: Preventing Catastrophes shows that there are still people who do not watch for Black Swans. Automation does not prevent catastrophes. Well, at least ones that you are not looking for already.
• Automate Salesforce Administrative Tasks with Selenium has the results of the contest they ran.
• ErrorList object for use in TestNG/Selenium testing is a soft-assert implementation
• Iterations has an outstanding time-lapse of how the Pycon US logo was designed. Someone should do this scripting out a website.

And my post that I’m going to link against is a bit of a rant around how to choose selenium training. Though it has also been pointed out that a lot it applies outside the scope of Selenium as well.