All of them are reporting errors because of a busted configuration of the docker image or test job.
I just had a look at the test failures you were mentioning. So I strongly advise you to check with the folks maintaining the docker images what’s wrong. Just to clarify here, I’m one of the maintainers of geckodriver, and nothing what you have written in the last comment is known to us. The easiest solution to keep your tests working is to use the selenium docker image that works I prefer to use both, so I found a working solution this is what I am sharing. I’ve read a lot on the web, seems like newer versions of firefox are reported as problematic and the common recommendation is just to use chrome instead. I did my own non-docker build with firefox version 46 and I was able to get that working with selenium. I’m not sure if it is a miscommunication between the mozilla folks with the selenium docker folks, or if it is just due to mozilla changes that they are unable to refactor. This is not just affecting me, it is affecting the entire selenium planet globally. The last standalone-firefox-debug build that says ‘Success’ is the one that contains firefox version 45. The only firefox version I got working was the one that passes selenium tests. Newer versions of firefox are not passing seleniums own build tests.
If you look on selenium docker page, they note that all firefox builds have failed since version 45. In my behat.yml I had to specify version 45īut when testing the latest selenium image selenium/standalone-firefox containing firefox 57.02 (asuming similar to firefox 58?) I tried with the recommended version * and also version 57 to no avail. The exact same test succeeds using selenium/standalone-firefox:2.53.0 contains firefox version 45 Meanwhile the exact same test succeeds using selenium-chrome-debug Using Firefox 57.02 with the latest selenium-firefox-debug docker image firefox was unable to find elements on a page, unable to find a form element. I am successfully using docker image selenium/standard-selenium-chrome latest version and docker image selenium/standalone-firefox:2.53.0 the selenium chrome docker works perfectly for me, and the older version 45 of firefox also works well. I discovered the selenium docker images and they are much more convenient for my needs.
#Building mozilla geckodriver drivers
I don’t have the mandate or budget to re-engineer the selenium drivers at this time so it was cheaper to downgrade firefox. “please let us know about misbehavior when using Firefox 58” That’s why please let us know about misbehavior when using Firefox 58, so that we have enough time to get it fixed for Firefox 59, or even 58. But please note that this workaround will only work for Firefox 58, and maybe Firefox 59, because then the old and legacy behavior will be removed. Simply set it to False, and the former behavior will happen. In case the problem causes issues for your test suites, but you totally want to use Firefox 58, you can use the capability moz:webdriverClick and turn off those checks. If you are hitting such a condition it would be fantastic to let us know about it as best by filing an geckodriver issue with all the required information so that it is reproducible for us. While pushing this change out by default, we are aware of corner cases where we accidentally might throw such a not-interactability error, or falsely assume the element is interactable. If you are asking now why this change was necessary, the answer is that we are more WebDriver specification conformant now. If not a not-interactable error will be thrown. That means that if such an operation has to be performed for any kind of element it will be checked first, if a click on it or sending keys to it would work from a normal user perspective at all.
For both commands we have enabled the interactability checks by default now. When you are using Selenium and geckodriver to automate your tests in Firefox you might see a behavior change with Firefox 58 when using the commands Element Click or Element Send Keys.
0 kommentar(er)
