A Smattering of Selenium #24

A bit late, but I’m in California for a Selenium Developers Meetup and my body doesn’t quite know where it is temporally.

• Don’t forget that tomorrow is the next meeting of the San Francisco Selenium folks which seems to be running a crowd sourced “Let’s stump Jason with our problems” session. Most of the ‘main’ Se folk will be there.
• Test design theory is something that I have yet to really see covered much, so here are three articles on the similar idea of what to test and what to skip.
  • Contradiction: Test Everything, but not Accessors? by Ron Jeffries
  • don’t test for blocking conditions: an example by Chris McMahon
  • Every automated test should do ONE thing really well by Adam Goucher (me)
• Another simple build radiator is just a darn cool re-skinning of Hudson which, while not as fun, is super useful in communicating build status
• Simon started to explain some of the work going on in the guts of Selenium WebDriver in Going Atomic: Why?
• For those people who loiter in the #selenium irc channel, you have likely seen ‘selbot’ in action. If you wondered where it came from you can read the details from Sauce Labs in Introducing selbot
• Atlassian is a pretty big user of Se and has a post called push my buttons which explains the myriad of ways you can send a key in Se 1.x. Which IIRC is one of the major improvements that Se 2 provides.
• The march of Flex Pilot continues and so the blog posts from users are starting to appear including Selenium Testing with Flex Pilot
• I was pleading for help on twitter last week and this cool use of the JUnit 4 @Rule annotation to get screenshots on test failures was provided
• If you are using CruiseControl.NET then Integrating Selenium Tests into CruiseControl.Net via NUnit is likely going to deliver value
• Silverlight UI testing with Selenium and Ruby is the first article I think I have seen on the subject. Of course, my memory isn’t so hot at time…

• Previous
• Next