-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Description
Not sure where to begin. I downloaded firefox-standalone-debug or whatever and spent some good time (12hrs+) working with it. It runs Selenium but eventually throws an error on driver.get, which seems to be linked to the FF version. I manually downgraded FF in the container and wound up with some other issue.
I originally tried these containers because somewhere between Selenium, Firefox, and Geckodriver versions, there are bugs in the dozen or so implementations I have tried. Ironically, I have been using Selenium standalone with FF for years and -never- had a problem until recently. I don't understand how something that worked so perfectly up to 2 years ago can now be impossible to get working 100% of the time.
I guess this is a bit of a rant. I'm just hoping that this git actually supplies something useful, like a working combination of the above-mentioned software versions. Can anyone recommend any combination of (docker containers, software versions, etc.) that will allow me to run Selenium tests successfully? I have spend hundreds of hours trying to work around all this BS ChromeDriver/GeckoDriver crap. It almost seems like these two new parts of Selenium were designed to break Selenium. Do people still use Selenium? I assume there is still some way in the world of producing a working Selenium implementation? Or did Selenium just cease to exist?
I realize I'm not providing much information but this is surely some kind of known "issue" (more like 20 issues). Selenium standalone has never worked for me under ChromeDriver or GeckoDriver, and I tried the server last night with a Docker container and am still encountering issues. I have given up on this. Can anyone provide a plan of action for producing a working Selenium environment, that does not have huge issues involving Geckodriver or Chromedriver, in under 10 hours?