![selenium ide firefox version support selenium ide firefox version support](https://i.stack.imgur.com/W1x8U.png)
Still, there were quite a few factors that made this state of affairs predictable.
![selenium ide firefox version support selenium ide firefox version support](https://www.lambdatest.com/blog/wp-content/uploads/2020/05/what-is-Selenium-IDE.jpg)
![selenium ide firefox version support selenium ide firefox version support](https://i0.wp.com/dumbitdude.com/wp-content/uploads/2017/08/Firefox-devtools.jpg)
In a way, the situation with Selenium IDE in Firefox proves that even great projects can become semi-abandoned at a certain point. In 2016, there actually was just one developer filing commits for Selenium IDE: Over the past couple of years, there’s been but a handful of contributions, with only 11 regular committers. While there certainly are many contributors backing up Selenium WebDriver, the situation is different for Selenium IDE.Īs it turns out, the IDE has been lacking developer support for a long time. Okay, the support of Selenium IDE in Firefox is a matter of rewriting the plugin, but how can this be a problem? Isn’t there a huge developer community behind Selenium? Sadly, everything is not that simple. Developers show no interest in maintaining Selenium IDE in Firefox xpi-based Firefox extension, Selenium IDE would have to be rebuilt to retain compatibility with the browser. xpi-based extensions lose compatibility with Mozilla’s browser starting from version 55. While these may sound great, there is an unpleasant side effect. In theory, better interoperability with Chrome and Edge may increase the number of developers willing to build new plugins to Firefox.
![selenium ide firefox version support selenium ide firefox version support](https://addons.mozilla.org/user-media/previews/thumbs/200/200460.jpg)
WebExtension promises better cross-browser functionality.In particular, developers will be able to produce extensions without in-depth knowledge of the Firefox internals. The WebExtension format is decoupled from the browser, which accounts for easier development.The reasoning behind this move effectively comes down to two points: Last November, Mozilla announced its plans to fully transfer Firefox extensions development to the WebExtension API. In case with a technology as mainstream as the world’s 3rd most popular browser, leaving things behind often means leaving developers out it the cold. Cheesy as this may sound, it’s painfully true for mainstream technology. To keep moving forward, you sometimes have to leave things behind. xpi format used in Selenium IDE, Firefox will move to WebExtensions So what is the reason for discontinuing the support for Selenium IDE in Firefox? There are two of them, actually. Maybe it’s due to this long history that the news of Firefox dropping Selenium IDE feels so unexpected.
#Selenium ide firefox version support manual
It’s lightweight, it automates UI tests by recording manual testing sessions, and it has been the official Selenium recorder for Firefox since forever.īuilt in 2006, it has long become the first tool that comes to mind when someone mentions record-playback UI testing. Selenium IDE certainly deserves credit for doing exactly what it promises. Thanks to Mozilla, this has become more obvious.ĭon’t get me wrong, having the UI testing functionality of Selenium IDE in Firefox was super-useful. We’ve all known for years that old-school record-playback tools underdeliver in the way of usefulness. Mozilla’s decision to cease the support for Selenium IDE in Firefox 55 has drawn the attention of the testing community to a long-standing problem. What makes Screenster better than the Selenium IDE + Firefox combo?Įnd of support for Selenium IDE in Firefox version 55 and newer (image credit: Freepik).What the future holds in store for Selenium IDE?.