Teammates: Upgrade Selenium to 3.x
With Java 8 not being a blocking issue anymore, we are ready to migrate to Selenium 3.
wkurniawan07
All 10 comments
Upgrading to Selenium 3.x, would make Geckodriver.exe be downloaded compulsorily. Is that fine?
Should I go ahead with it?
tshradheya
on 22 Jan 2018
That is part of the expected work.
wkurniawan07
on 22 Jan 2018
Okay. Thanks 馃憤
tshradheya
on 22 Jan 2018
I have a query. On looking at the TEAMMATES documentation, it says only firefox version till 46.0.1 is supported. I am currently on that version and after integrating geckodriver , i am unable to make the webdriver open.
On looking up the geckodriver releases it says the following:
I am assuming the web driver will only work after i update my mozilla( I haven't tried that yet).
Just wanted to check what is the reason behind limiting the version to 46.0.1? Is it fine if we use the latest version of firefox for testing? Or are we limited to using till 46.0.1 currently?
tshradheya
on 22 Jan 2018
@tshradheya You are right, you need to upgrade to a newer version of Firefox in order to use geckodriver, and I think it may be a good idea to use the latest version. You can try checking the version support for the implementation of FirefoxDriver that is developed by Selenium and the implementation of FirefoxDriver provided through geckodriver (developed by Mozilla).
Bugs come and go in geckodriver as well, so there can be regressions when using newer versions.
LiHaoTan
on 22 Jan 2018
@LiHaoTan So can I assume its fine for us to update to a newer version of Firefox (i.e. 46.0.1 + ?)
tshradheya
on 22 Jan 2018
@tshradheya definitely, otherwise there would be no way to upgrade to Selenium 3.
LiHaoTan
on 22 Jan 2018
Query.
In the .travis.yml , I wanted to know how the firefox path is transferred to TestProperties ?
I want to use the similar method to export the absolute path of geckodriver and use it to setProperty of the System
tshradheya
on 22 Jan 2018
Just wanted to check what is the reason behind limiting the version to 46.0.1?
I believe it's precisely because we're using Selenium 2.x, which doesn't support later versions of Firefox. It'd be great if you're successful in upgrading to Selenium 3.x so we can finally use the latest Firefox.
whipermr5
on 23 Jan 2018
Resolved in V7.
wkurniawan07
on 22 Jan 2019
Related issues
whipermr5
路
4Comments
whipermr5
路
3Comments
xpdavid
路
3Comments
whipermr5
路
4Comments
damithc
路
4Comments
Most helpful comment
I believe it's precisely because we're using Selenium 2.x, which doesn't support later versions of Firefox. It'd be great if you're successful in upgrading to Selenium 3.x so we can finally use the latest Firefox.