does anybody have a problem of selenium tests failing on new safari version 13.
Ran the same tests on chrome and firefox and it works fine. Also tested it on older version of safari and it works fine.
I didn't manage to pin point exactly where it fails. One case I did notice is that on safari 13 selenium click on <div role='button' aria-haspopup='true'>....</div> invokes no action(in my case opens a popup menu). And test proceeds to the next line of code. note however at this point I am not claiming that this kind of click always fails, it's just where I noticed it in my tests.
If anyone came across this kind of issue on safari 13 please provide your input.
Thanks
Safaridriver maintainer here.
This is a known issue that we believe has already been fixed in Safari Technology Preview Release 91. Please verify whether the issue reproduces using latest STP's safaridriver, and reach out to me on Twitter, #brrian.
There is an issue with SafarDriver or Safari 13. Please vote the bug in WebKit https://bugs.webkit.org/show_bug.cgi?id=202589
I am also facing the same issue with Safari 13.0 and Safari 13.0.1. Till Safari 12.1.2 everything was working as expected but since my browser updated to v13.0 selenium script is broken.
I observed that Selenium clicks on other locator instead of the target (identified) locator. For ex. if you want to click on a button (//button) it clicks on the //div which is the sibling node of that //button in the DOM.
My workaround solution:
As I didn't update MacOS Catalina yet and only Safari 13 was updated; I was able to download the "MacOS Mojave installer". Then, I installed it as an update; resulting it rolled back my Safari version from 13.0 to Safari 12.1.2. Now my script started working again!!
Related
As stated, I am trying to use webdriver.Chrome in this sample project I'm doing but I am completely lost on what to do. This is the error I get error. But when I look at the version of chrome I installed, it seemed to match up. Chrome Version. Does anyone know what's happening? Sorry if the post is too unspecific.
You have to update your chrome browser. Try to update the installed chrome version to latest version.
To overcome this problem, use WebDriverManager: refer - https://bonigarcia.dev/webdrivermanager/ and https://github.com/bonigarcia/webdrivermanager.
If you are using Python with selenium, refer to this post for sample code:
Chrome with WebDriver--Why is it disappearing as soon as I hit "run"? Chrome Driver version 106 but Chrome can only be 105.0.9
If you are using Java with selenium, refer to this post for sample code:
element click intercepted in Selenium wedriver
I recently had a new VM created for Windows 10 and our test automation suite.
After I got everything installed, I ran some of our tests. However, every single time that Selenium launches ChromeDriver, I still see the "What's New" / chrome://Whats-new tab in the browser, then our tests launch in a new tab. The tests seem to work just fine, however, if I do have a failing test, we take a desktop screenshot, and of course, all we see is the What's New tab, not our actual site-under-test.
I do not see the tab when launching Chrome manually, on any user that logs into the box. It only happens with the Selenium-ChromeDriver launched browsers. Even closing the tab while a test is running doesn't permanently remove that tab.
I have never encountered this problem with ChromeDriver before and it's a difficult question to search for answers.
Chrome / ChromeDriver versions: 98.0.4758.82 (which was released on 2/2, but it also happened on the previous version)
Has anyone solved this problem recently?
Try to use chromeOptions.AddArgument("--disable-features=ChromeWhatsNewUI");
Anyone knows of any update from Safari team on this issue or has found a workaround?
Selenium tests broken by recent update of safari to version 13?
The GitHub issue is still "Open", and last comment from Safari driver dev was "It is being investigated", so we can assume the issue has not been resolved:
https://github.com/SeleniumHQ/selenium/issues/7649
The related WebKit bug is also still open:
https://bugs.webkit.org/show_bug.cgi?id=202589
I'm executing some tests after updating all my libraries to the last version like webdrivermanager (v 2.1.0) and selenium-java (v 3.8.1).
Everything was right when I execute them on Chrome, but after testing on firefox i got an issue.
I'm executing
myElement.sendKeys(Keys.TAB);
But i'snt working just on firefox.
After some digging on other forums it's seems that this problem is recurrent in some firefox versions.
Anyone already got this issue?
Edit¹:
I found that the problem is when using firefox, 'focusout' event is not firing when Firefox window is not really on focus.
That is a problem because I run test's in parallel, even when I'm debugging with IDEA on focus the event doesn't fire.
I got no error output when this happen. It's just dont fire 'focusout' javascript event.
I'm using:
selenium-java version 3.8.1,
Firefox version 57.0.4 (640bits),
geckodriver version 0.19.1.
I have a question regarding Selenium and the current Microsoft updates:
I just installed the newest Microsoft patches on a PC and now the Selenium scripts won't work anymore. I'm using the Selenium IE Driver 2.44.0 in the scripts. Maybe something has changed in the Internet Explorer, I'm not sure. Suddenly the scripts can't find any web elements on the page anymore. An InvalidSelectorException is thrown because the findElements methods can't be executed. The IE driver opens up and it navigates to the given URL, but when it tries to find a web element, the script fails. I also tried it out on a PC which hasn't the newest updates installed yet and the scripts are working fine there, there are no problems at all.
Do you have any ideas what to do or what could be the cause?
Thanks a lot!
Yes as I stated here
If you have taken windows update KB3025390 IE will not work as expected. There is currently no resolution to that yet.
Also, Uninstalling the update KB3025390 should make the WebDriver work correctly with Internet Explorer 11. See this answer