Im trying to use JMeter with the Selenium WebDriver plugin to do some testing. I know that it requires Firefox v. 26, however I find this to be pretty useless given that testing on anything besides the most recent browser version is pointless, as that is what users will be using.
Using the current WebDriver plugin with Firefox v 50 results in the 'browser.get()' not working. Is there a way to get the plugin to work with Firefox 50?
The latest Selenium/WebDriver Support plugin available via JMeter Plugins manager as of now is version 1.4.0. It comes with selenium-firefox-driver-2.52.0
It means any browser supported by Selenium 2.52.0 will be supported
Looking into Selenium Changelog Selenium 2.52.0 supports Firefox 45 which is an ESR release according to Mozilla FAQ:
I don't know where did you get the information regarding Firefox 26, I would recommend upgrading to Firefox 45 which should be supported till June 2017 and hopefully JMeter Plugins maintainers will upgrade Selenium libraries to version 3 by that time.
In general WebDriver will be always behind the browsers development so you will have to live with the supported versions.
References:
JMeter Plugins Forum
The WebDriver Sampler: Your Top 10 Questions Answered
Related
Previously I was using Selenium version 2.53 with Firefox version 40.0.1. But now Firefox is updated and I am trying to do with updated version.
So, respond me about "which Selenium JAR is compatible with Mozilla Firefox version 59.0.2 (32-bit)"
As per best practices you must adopt any one from the below mentioned configurations:
Last weeks there has been a lot of noise about this new FirefoxDriver called Marionette. To use Firefox with Selenium, we used to use the "old" Selenium FirefoxDriver. From Firefox 48.0 onwards it is going to be required to use this new FirefoxDriver developed by Mozilla.
I understand it is required to change to that direction to get every browser supports and develops its drivers and to get drivers independent of Selenium. Besides, it is supposed if Mozilla develops its own driver, it will be faster and easier to fix issues and to develop features.
My question is, for those who create automated tests using Selenium framework, is there any benefit of using Marionette instead of the "old" Selenium supported FirefoxDriver? _(Such as a better performance, a better compatibility...)
The main advantage for using the Mozilla-provided, Marionette-based Geckodriver solution is that it works for versions of Firefox 48 and higher. The legacy driver provided and maintained by the Selenium project doesn't work for Firefox 48 or higher, and will never work for those versions of Firefox.
The legacy driver is implemented as a Firefox extension. This extension is installed in the profile used by the driver when WebDriver launches Firefox. Firefox 48 introduced two new features that disabled this browser extension. The first is the so-called "electrolysis" feature, or multiprocess Firefox. Electrolysis changes the way extensions have to deal with the browser in ways the Selenium team has not taken the time to fully understand.
The second, more important requirement is that all browser extensions must be signed by Mozilla before the browser will allow them to load. This latter feature has been in Firefox for several versions, but beginning with 48, it can no longer be disabled. The WebDriver browser extension introduces several valid security concerns for the Firefox browser, and as such, will not be signed by Mozilla's security team. This, in turn, renders the extension inoperable, and thus Selenium can no longer communicate with Firefox. The Marionette-based solution, being developed and maintained by Mozilla in the first place, is blessed by them for use in automating Firefox, and as such carries a commitment that it will continue to work with future versions moving forward.
So the primary benefit of using Marionette with Firefox 48 and higher is that it will work, whereas other solutions won't.
What is the version compatibility between chromedriver and selenium-server-standalone.jar?
In other words, does latest version of chromedriver work with latest version of selenium-server-standalone.jar?
The Chrome Driver itself is tied more to the version of Chrome available on the execution Node (where the browser is actually spawned and a test is ran).
If you refer to the release notes, you'll see how the driver versions map to the various releases of Chrome itself.
The practice I have in place is as follows:
I match my Selenium dependency (C#/Java language bindings) to the version of the selenium-server I run either locally or on my Grid.
When I deploy a version of my test project that upgrades the Selenium dependency, I simply upgrade all my Grid VM's to the matching version (using JSON Node config really helps here, since all I have to do is stop the service, swap the jar, and relaunch with my JSON configs).
Firefox Driver is built into Selenium, so no upgrade management there. IE Driver has (at least historically) matched the minor version number of Selenium (for example, current IE Driver is 2.48.0 while Selenium is at 2.48.2), so I typically upgrade my IE driver whenever I upgrade my Selenium version. The version of Chrome Driver I employ on any given Node will then correspond to whatever version of Chrome that particular Node has installed, though in my own case, this is typically the most recent version.
In short, it's more important to match the version of Chrome Driver to the version of Chrome under which you are testing.
To add my 2 cents, chromedriver acts as the "bridge" between Chrome and the Selenium jar, so on one side you have the protocol and interface (WebDriver) that is backward compatible and on the other you have dependency on browser's releases which isn't. So compatibility wise #tim-slifer's answer is sufficient (except that now Firefox also has a driver).
However, when consuming the selenium-server-standalone.jar, you consume a binary. So versioning wise, keeping up to date with the Selenium releases is simply to have fixes to new issues that rise with time - some of which related to the compatibility between chromedriver and Chrome.
So yes and no, there is some compatibility between the 2, although an old jar and bindings can work just fine with new browsers.
I would like to run my Selenium WebDriver tests on Opera, but when I had a look at the Opera driver at Selenium HQ and GitHub page, it says:
Opera Driver requires Opera 12.x and older versions
Note that OperaDriver is only compatible with Presto-based Operas up until 12.16. Blink-based Operas (15 and onwards) are not supported.
Opera is now up to version 22.0, so far beyond the maximum supported version of 12. So, my questions are: -
If there is no Opera driver for Selenium, then how does one automate Opera tests?
It seems strange to stop at version 12, even taking the underlying technology change into account. Is Opera support waning or is it that Selenium WebDriver is no longer the best tool?
Opera has just released an early beta of WebDriver for their Blink based browsers. See https://github.com/operasoftware/operachromiumdriver
To quote from the link provided:
OperaChromiumDriver can be used without extra setup on Chromium-based versions of Opera starting from version 26.
For driving Presto-based Opera browsers, refer to the OperaPrestoDriver project.
Although versions earlier than 26 aren't officially supported, the OperaChromiumDriver v. 0.1.0 works with Opera 25. On Windows using the 'binary' option in 'operaOptions' may be needed.
Download OperaDriver from here and write the following code for java:
System.setProperty("webdriver.opera.driver", "D:/Ripon/operadriver_win64/operadriver.exe");
WebDriver driver = new OperaDriver();
driver.get("https://duckduckgo.com/");
1 & 2)
There are 2 types of Opera - Java Based and Chrominium based.
The provided links are for Java based Opera.
https://github.com/operasoftware/operadriver#desktop
There is no official support for latest Opera versions.
Looking at Platforms Supported by Selenium the highest version of selenium supported is v 10. I am assuming this is in line with 10 being the current extended support release, v17 is the next ESF, due out on 20 Nov 2012
Firefox extended suport
Firefox release calendar
However looking at the release notes for the Selenium client driver 2.25 (18 July 12) it says "Updated supported versions of Firefox to 17"
Which page should we read? How does the Platforms Supported by Selenium page relate to the 2.2.5 release?
You should refer to CHANGELOG. Thats always the latest. Seleniumhq.org gets updated by someone manually... Which is not happening regularly I guess.
I use selenium 2.25 and I had to download to Firefox version 14 in order to get selenium to work correctly.
Other people have documented this issue but I haven't found any resources that say what versions of Firefox are supported for each version of selenium.
selenium-firefox-driver 2.25.0 not working correctly with Firefox 15
Also if you are using selenium with your web browser you are going to have to turn off automatic updates on your browser to prevent it from updating.