Who knows in which release of selenium server firefox4 (firefox5) works correctly. On http://seleniumhq.org/about/platforms.html mentioned that both versions are supported, but I didn't find in release notes anything like Fixes of Firefox4 support
The new server (selenium-server-standalone-2.14.0.jar) runs with current versions of Firefox (8.x)
Selenium RC 0.9.2 should run FF4
you can download newer versions also they have only one jar file. or even edit older versions to support for newer versions of browsers ?
Related
For my app i need FFmpeg, so i went to official website, for windows builds it said go here :-
https://github.com/BtbN/FFmpeg-Builds/releases/tag/autobuild-2021-01-20-13-01
But now i have a problem.
Which version of ffmpeg is newer ?
ffmpeg-N-100679 or ffmpeg-n4.3.1-29 ?
Is that "N" version unstable and "n4" version stable ?
Any help would be appreciated 🙂
Which is newer?
ffmpeg-N-100679-g24dc6d386c is newer. It is from the git master branch, and is a snapshot of the current, up-to-date FFmpeg code for the date it was released. It corresponds to commit 24dc6d386c (note I omitted the g prefix) which is from 2021-01-20.
4.3.1 is from 2020-07-11. Since new features are not backported to release versions (only certain bug fixes) it is just an extension of 4.3 which was released on 2020-06-08. The FFmpeg Download page contains the dates for releases.
So ffmpeg-N-100679-g24dc6d386c is about 7 months newer than 4.3.1.
Which do I use?
ffmpeg-N-* for general users. If you want the latest code and features. Required for anyone who wants to submit a bug report. If you experience a problem with the newest release. It is stable ~98% of the time I'd guess from using it over many years.
Release version: if you are required to stay within a certain API version. For distros, distributors, users of the FFmpeg libraries, etc.
Versions with N-xxxxx are nightly builds / snapshots and are unstable (but newer). Use them only for testing or if the last release has a bug that is already fixed and only available in the nightly.
Otherwise I recommend to use the latest release (currently 4.3.1). This is typically more stable.
I ran into an issue today where my preview server was running an older version of a project instead of the most recently published version. The most recently published version was 1.0.4.10, but after some testing, I determined that version was not the version of the application that the server was retrieving.
After trying a few things, I tried publishing a new version under 1.0.5.0 instead of continuing with the 1.0.4.xx numbering, and that fixed the issue.
VS's auto increment feature recommended 1.0.4.10, but is there an issue with this being the same as 1.0.4.1? So maybe it was running 1.0.4.9? Or something behind the scenes I'm not aware of?
Problem How can I ensure correct browser versions at test execution time for selenium to run against?
Given that selenium requires specific browser version and I don't want to manage installing and updating versions on win (lin would be easier via puppet) I need a way to deploy the right browser version during my build.
Is this what other folks are doing?
bundle firefox, chrome browser versions as archive files
deploy these to my maven repository (nexus)
at build time use dependency plugin unpack goal to extract browser archive to target//
at test execution time, feed in location to browser executable and use that with selenium driver
Or is there a plugin that already handles this for me and am I re-inventing the wheel.
Thanks for the help.
Peter
This ceased to be an issue as my team decided to use chrome not firefox. So, here's the whole process for handling chrome driver and unpacking chrome. you can easily adjust it for firefox.
https://stackoverflow.com/a/38984738/9950
I have cucumber scripts running currently on chrome browser version 25. A update on chrome version had happened recently and I see that all cucumber jobs are failing. Please advice with necessary changes to be made can overcome this problem
If we choose latest version of Firefox or latest version of Selenium-Webdriver, we couldn't automate few tests because of either something not supported in latest version of Firefox or latest version of Selenium-WebDriver.
In such situation, which combinations of Firefox version and Selenium Webdriver version should we choose? (I mean, should we go for one/two version back of latest Firefox version and/or one/two version back of latest selenium webdriver version or some other combination?)
The Latest piece of softwares are always preferable, But the selection of browser version is highly depend upon your application under test.
For newer versions of selenium (v3), check out the selenium-docker releases here, https://github.com/SeleniumHQ/docker-selenium/releases, you can even use docker to test all the Selenium/Firefox combinations easily. For older versions of selenium (v2), check out the selenium site here, https://www.seleniumhq.org/about/platforms.jsp .
I recommend moving to the docker path for local testing; then you can also use the docker files to migrate to cloud platforms.
Use whatever your acceptance criteria states. If you have to support an earlier version of Firefox because it is in a contract or requirement, then you must test that version and use whatever version of selenium is necessary
When ever you download latest webdriver version, make sure that you look into https://raw.githubusercontent.com/SeleniumHQ/selenium/master/java/CHANGELOG
to check the latest browser version support.