Selenium 2.6 Released
If you’ve been watching this blog carefully you’ll have noticed that the last release announcement we made was for 2.3, so it may come as a surprise that we’re announcing that 2.6 has been released (even on Maven!). Don’t worry: 2.4 and 2.5 were released on time and without muss or fuss. 2.6, on the other hand has been almost three weeks brewing.
Selenium 2.6 introduces a raft of improvements and stability fixes. Kristian Rosenvold has been working wonders on Grid 2.0, addressing many reported issues and cleaning up the implementation. In the finest tradition of the project, I now owe him a dinner for his hard work. Thank you, Kristian!
For those of you not using Grid, as well as the normal suite of bug fixes, Selenium 2.6 now supports all versions of Firefox from 3.0 up to 7. For those of you using Java, there is an ExpectedConditions class that supplies many useful criteria when using the Wait and WebDriverWait classes. The packaged version of the OperaDriver has also been bumped to 0.7.2, which works hand-in-hand with Opera 11.5 and above.
We’ve also spent a considerable amount of time and effort working out the kinks in the Advanced User Interactions API. We’d love to hear how you’re using it, and what the gaps are that you can see. For more details about what’s changed, have a look at the release notes.
The release frequency has dropped recently, but we’re planning to head back to weekly releases from here on in. 2.7 is just around the corner!
Share this:
A Smattering of Selenium #58
And here we go again with more links than I thought I had collected…
- There are a metric tonne of site on the internets which are on how to scam your way through a Se interview. Hiring Selenium QA people provides some fodder on how one could look for and hire Se folk.
- Why I don’t use spork reminds us that pain is [sometimes] a good thing.
- The Jenkins project is having a conference on October 2 in the same hotel that SeConf was held.
- So long, farewell, and thanks for all the automation lessons learned (or: o hai beautiful Page Object Model AMO Selenium tests!) could win the prize for the longest title ever. And has a good lessons learned section at the bottom.
- Selunit lets you run your Selenese inside something like Jenkins
- ATDD is still ‘the next big thing’, but Raconteur seems pretty darn cool. If I worked in C# that is…
- From Agile 2011 we have
Pay close attention to the database section. I’m getting more and more convinced that this is the part that most companies can benefit the most from.
- How to get the args of a function in Python is one of those geeky things that is super helpful and likely a smell that you are trying something you shouldn’t be at the same time.
- Is your test automation actually agile? A Guardian Content API example. is part two of one linked in the last Smattering. And the last paragraph is so full of win.
- Our friends at Watir have released Watir 2.0. Congrats!
- I’ve not tried to run Cucumber in Jenkins, but explains how to do it should you have need
- More people should make logos out of lego.
- Waiting for elements when UI-testing with WebDriver and EPiTest explains a bit about the WebDriverWait class and has The road to UI-testing hell is paved with Thread.Sleep which would get it linked to in any event.
- One thing that keeps getting brought up around WebDriver is ‘how do I get the http code of a request?’. The short answer is you don’t. The long answer is you have to do something like HOWTO: Collect WebDriver HTTP Request and Response Headers
- How Cadence Predicts Process reminds people to look at all parts of the process when speeding things up
- When building frameworks or DSLs it is useful to know how to make things as deprecated. deprecatable is one way to do it in Ruby
- Exploratory Testing in an Agile Context is another session handout from Agile 2011.
- #Selenium Tales from the road part 1 – Artifact Naming and Organization describes one way of organization your Se stuffs. That you need a convention I think is exactly why you should use dynamic suites via tags, but…
- The PyCon US 2012 Call for Proposals is now out.
- Continuous Deployment of iOS Apps with Jenkins and TestFlight describes how to build iOS apps in Jenkins (and if you want, pushing them up to TestFlight)
- Why oh why am I only just discovering requests which makes Python’s urllib2 usable.
- How to be a faster writer isn’t about writing scripts or code, but its ideas are still sound.
- I pretty much refuse to read anything in ACM format, but On the Criteria To Be Used in Decomposing Systems into Modules could be of interest to someone without my biases.
- An Inside Look at the GIL Removal Patch of Lore is the geekiest bit of writing I’ve read all month.
- I had forgot how much I enjoy purpose built sites like Is the internet down?
- I did a webinar on Page Objects the other week for which the video is now available. Its not embeddable, but there is at least a link around the registration wall above the form.
Share this:
A Smattering of Selenium #57
Phew. The links made it through the Lion installation.
- Distributing the Same Test to Multiple Processes shows a technique for debugging flaky scripts
- Repeat after me: I will not automate GMail unless I am Google. Or if you will, you will do something like what is described in Verify email confirmation using Selenium. Notice that they are not using Se for it.
- Selenium and Nagios is something more teams should do I think.
- ‘This started out as a…’ usually means the discovery of a rabbit hole. Towards better acceptance test automation… has a great diagram where all roads lead to accidental complexity and The A Team the proposes solutions to those complexity problems.
- Specialized Skills remarks that ‘life is like a box of crayons’ — I’ve been having this conversation around automation again recently. When everyone blurs their specialization boundaries you have a [chance] of success.
- Performance Testing Practice Named During Online Summit names a practice we’ve often used — User Experience Under Load
- Introducing page-object gem showcases a pretty nice looking gem.
- Often people link to W3Schools.com when explaining XPath, CSS, etc. Please don’t. W3Fools explains why.
- Is there another Se-in-the-cloud provider coming? The testingbot gem seems to imply so
- FluentLenium lets you write JUnit scripts that look like JQuery code
- Mining Cucumber Features has a cool investigation trick that could be adopted to larger scopes than just cucumber
- Image to CSS Conversion with Img to CSS API is likely something I would explore if I was going to compare page image contents.
- Selenium IDE I think runs afoul of the attractive nuisance doctrine
- Are you a tool vendor? Here are some steps you can take to avoid a curse being placed upon you
- Test automation that helps, A Guardian Content API example is a bit of an exploratory automation experience report but also reminds that the point of all this is to get new information.
- Your Chrome browser might not be using HTTP anymore is my new Example One for why the browser vendors need to be the ones to provide the automation hooks. Which in this case, they do.
Share this:
