Selenium Blog

I’ve missed a couple weeks due to travel and a complete system lock which meant I lost all the links I had open but not saved. So these are the ones I have recovered.

• I have written a series of posts on how to do parallel execution of tests in JUnit 4 up on the Sauce Labs blog. Part One, Part 2 and Part Three
• Quick start with FitNesse and Selenium is a beginners guide to wiring Selenium and FitNesse together. Though it might have been easier to just use Selenesse
• Meetup: Test Automation Tips, Techniques and Best Practice – Ruby and Java night in NYC, November 8
• Commit 10000 for the Se project. That’s a non-small number
• If you are using Maven 3, you can now use the Selenium Plugin with it now.
• Do Testers Have to Write Code? applies to Se as well.
• Multiple Sessions in Cucumber & Selenium got a fair bit of twitter love and is something I’m seeing clients want/need more and more
• A Set of Principles for Automated Testing is not a bad list. I completely disagree with the second one, and the last one is blatant employer promotion (but is contextually correct).
• RSpec best practices is a similar list which I have less complaint about. The third point is likely the most important one.
• Multiple Sessions in Cucumber & Selenium is a solution for when you are testing something with WebSockets with Cucumber.
• NUnit 2.5.8 is out.
• Dale Emery has released Runtime Suite which is super handy for creating test suites at runtime with JUnit 4. It doesn’t (yet) work with parameterized classes, but is still pretty cool
• Feed4JUnit seems to have don’t some of the legwork for people to do parameterized JUnit scripts. (Yes, I’ve been stuck in Java-land for the last while; why do you ask?)
• As Flex Pilot gets more usage, things are starting to trickle out into the blogs. Automating MyAppInFlex.swf – Useful FlexPilot commands is one of those posts.

Oh, and both 2.0a6 and 2.0a7 have been released. We’re getting closer to the ‘API freeze’ which will mark the end of ‘alpha’ and the start of bug fixing (beta) for the final release.

Share this:

We are extremely pleased to announce the release of Selenium 2.0a6! Head over to the downloads page to get it while it’s hot, or wait just a little bit longer for it to appear in a maven repo near you. The .Net version will also be updated soon too, and the python and ruby libraries have been having smaller, more frequent releases all this time.

You’ll be pleased to hear that the Selenium 1.0 APIs have remained constant, so what’s changed? Here, in no particular order are the major changes you’ll find in 2.0a6:

• Android support: you can now download the APK and run webdriver tests using Android 1.6 to 2.2.
• Firefox 4 support.
• Experimental IE9 support
• New APIs for dealing with HTML5 elements (best implemented, for now, by the mobile webdrivers)
• A richer .Net API
• A move to Sizzle for locating elements using CSS in browsers that don’t have a native API for that.
• Far better support for running your existing Selenium RC tests using WebDriver, helping you make a managed migration to the newer APIs.

There are also lots of nice touches for the more technically inclined, including the ability to re-use instances of FirefoxProfiles, better configurability when requesting a remote webdriver instance, better resource management and more shared code between the Selenium and WebDriver implementations.

Thank you to everyone who has taken the time to report a bug on our issue tracker, or raised problems on one of our mailing lists, or shown up for some of the banter on the IRC channel: without your involvement, the project wouldn’t be half as much fun, and wouldn’t be as capable as it is. Thanks are also due to the development team, who have poured an enormous amount of work into this release (538 revisions in under 90 days, or about 6 check-ins each and every day)

Hope you like it!

Share this:

A fair number of links this week. The vast majority of which were buried in annoying airport internet advertising frames…

• This looks like it is Spanish which would normally mean it doesn’t get included but it Integração Selenium e Testlink explains how to integrate Se with TestLink. We, as a community, need to document this sort of thing more.
• JUnit 4 Vs TestNG is a somewhat biased comparison between JUnit 4 and TestNG; but useful none the less.
• Hot on the heels of last week’s SFSE is the announcment of Learn to Test Your SproutCore Apps with Lebowski Framework for the month of October.
• Behaviour Driven Development With JBehave Web 3, Selenium and Maven 2 on OS X Snow Leopard is, aside from very buzzword compliant, the first thing I’ve seen using Se and JBehave.
• Bi-Testual: Coming out of the Software Closet is something a lot of people in automation grapple with. Am I a tester who programs? A programmer who tests? Something entirely new?
• Using Selenese and want to use Sauce OnDemand? Absolute Beginners Guide to Running Sauce RC with HTML Scripts is for you.
• While combing the Sauce Labs blog, I noticed my How To Minimize The Pain Of Locator Breakage has been published.
• Page Objects are ‘in’ to say the least these days. Writing page based tests with selenium in ruby is just enough to get you down the path of page objects in ruby.
• And because we can’t have only one post on Page Objects, Step-by-step selenium tests with page objects, dsl and fun! is in Groovy
• Cheatsheet: Creating mocks in PHPUnit could be useful for those who write Se scripts in PHP
• The talks for GTAC 2010 have been announced. I don’t know what the pool of talks they pulled from was like, but I’m underwhelmed
• I have no idea where SeleniumWiki came from, but there is a fair bit of content there. Not sure how much is original and how much is lifted from other places on the internets — the spidey sense tingles when the title says ‘VB Code’ which seems to imply it is an SEO hunting site.
• Martin Fowler’s DSL book is out Real Soon Now and the first chapter is available online. Most people have been saying ‘build a DSL for your scripts’ for awhile — now we’ll see just how off all our definitions of that were.
• getXpathCount is one of the more powerful commands in Se, but the bulk of people use it ‘wrong’. Effectively using Selenium’s getXpathCount function starts to address that problem.

Share this: