After a considerable period of investigation and bug fixing in collaboration with the Selenium project and the Legion of the Bouncy Castle, we are happy to announce we’re moving to Selenium 2.30.0 as the default version in our service. You can find more details about this release in the official changelog.
This transition is scheduled for Friday, March 1st. In the meantime, we advise you to try your tests on this new version by adding the following key-value to your tests’ Desired Capabilities:
"selenium-version": "2.30.0"
If you see any issues after moving over to this new version, we definitely want to hear about it. And remember, once we move everyone to 2.30.0, you can still keep your tests on our previous default (Selenium 2.18.0) version by using the “selenium-version” capability outlined above.
Happy testing!
Hello Santi,
So, is there any specific reason to freeze 2.30 as a default one ?
Regards,
Manoj
Oh, the plan is not to keep it as default for too long, but until we decide there’s another version ready for prime time.
Although the project does a great job at maintaining quality, all of our customers’ tests are our responsibility, so we can’t take upgrades like this lightly. Every version needs to go under weeks of scrutiny before we can commit to inform all our users and do the move to a newer and better Selenium.
Hey Santiago,
2 questions:
What does default version really means?
Does selenium 2.30 bring a better performance of the HtmlUnitDriver for headless testing?
Hi Mademba,
Default version means that if a user doesn’t request a specific version of Selenium using their desired capabilities, we’ll do it for them, and in those cases, 2.30.0 will be the one we choose.
Regarding performance in HtmlUnitDriver, that’s not something I’m very up-to-date with. The changelog or the dev users group is probably the best place to get a good answer.