Tuesday, January 22, 2013 by shs96c
A Plan to Drop Firefox 3.x Support
The support policy of the selenium project for Firefox browsers is to support the current and previous stables releases, as well as the current and previous ESR releases. At the time of writing, that means the supported versions are “10” and “17” (ESR) and “17” and “18” (stable channel). In addition to this, we are currently supporting Firefox 3.x too.
This is an official announcement that we are planning to end support for Firefox 3.x in the near future in RC, WebDriver and Core/IDE, and this is your chance to be involved in that decision. Unless there is a strong reason to do otherwise, I shall shortly be announcing a timeline for the end of the support of 3.x
Once support for Firefox 3.x is removed, the earliest supported Firefox version will be the ESR-1 release (currently Firefox 10).
Rationale:
Firefox 3.x is no longer actively supported by Mozilla, and this has been the case since April 24, 2012. Since this time, 3.x has dropped to under 1% of global Web traffic (0.62% at the time of writing according to StatCounter) Continued focus on supporting an effectively dead browser prevents the selenium team from using features in the newer releases for little benefit to you.
Continued support of Firefox 3.x by the selenium project gives the impression that that particular version is still a valid option used by the population of the Web. This is simply not the case, and it may mean that testers efforts are being spent fixing problems that almost no users will ever see.
What you can do:
If you agree that this is the right choice, then you do not need to do anything. If you disagree strongly and have the numbers to back up your position, particularly if you can help work on Firefox 3.x support, then please reply to the selenium-user google group.
On a personal note, I know that a lot of you may well have firefox 3.x support in your test plans and will be distressed by this plan. Please take the time to look at actual usage logs from your sites and applications to verify that continued support is worth your time and energy before responding. I’d really appreciate that.
Share this:
Tuesday, January 22, 2013 by shs96c
Selenium Conf 2013: Call for Papers and Early Bird Tickets
This year’s Selenium Conference is slated for June 10 – 12 in beautiful Boston, Massachusetts. The conference will be held at the Renaissance Boston Waterfront Hotel. Similar to last year, this year’s conference will kick off with a full day of Selenium Workshops, followed by a two day, two track conference. If you’ve always dreamed of speaking at a Selenium Conference there’s still time to submit a talk to us at http://www.seleniumconf.org/speakers/.
As we have done every year, we’re pleased to announce that a batch of early bird tickets to the Conference is on sale now, even before the talks have been finalized. You can get your ticket(s) by visiting http://seconf2013.eventbrite.com/. There are only 45 early bird tickets available at the special rate of $299, and they are only available until February 4th, so act now! After that the regular price of $350 will be in effect for all tickets. You’ll also notice that tickets to our workshop day are for sale as well. These cost $75 and entitle you to attend a full day of Selenium workshops on Monday June 10th.
More information on the conference is available at http://www.seleniumconf.org/, and we are still accepting speaker proposals. We’re looking forward to seeing you in June!
Share this:
Monday, January 21, 2013 by adam goucher
A Smattering of Selenium #138
<insert snark here>
- Debugging For Testers — they don’t teach this in testing school. Actually, there is a testing school…
- A million times this!! That’s not BDD, that’s just Cucumber
- Faster Websites: Crash Course on Web Performance — all three hours of video
- Continuous Integration of iOS Projects using Jenkins, CocoaPods, and Kiwi
- Clearing IE’s Caches – Not as simple as it appears is another one of those things that gives Jim headaches.
- Speaking of things that give Jim headaches; Revisiting Native Events in the IE Driver. Fun, fun, fun.
- We’re Doing It Wrong! What DevOps Needs to Learn in Order to Scale Up. is pretty good, but wow I dislike this slide system.
- why GNU grep is fast – The key to making programs fast is to make them do practically nothing
- Squash feels kinda like a wrapper about ‘git blame’ coupled with a log monitor, but still an interesting concept.
- Writing faster WebDriver tests isn’t necessary making scripts faster as it is about a clever abuse of the JS Executor
Share this:
