Does selenium webdriver 2.53.0 support safari on Windows? - selenium-webdriver

I'm trying to automate my test suite on Safari 5.1.7 on Windows 8.1. I did install the extension provided in Seleniumhq.org. But I'm getting an error saying
Exception:
Did not receive a connection from the Safari extension. Please verify that it is properly installed and is the proper version..
I'm struggling with this since a very long time but didn't receive any help. Googled a lot but left unsuccessful. If anyone is automating safari on windows please help me.
Followed the steps mentioned here.
According to this post on SO, Is it worth downgrading for Safari? I could run my test suite on IE11, Firefox, Chrome and Opera. Can someone please guide me with this issue.
Thanks.

Using Selenium Webdriver 2.47, we can automate safari on windows platform. Source from here.

Related

Issue with running selenium scripts in headless browser in gitlab CI beacuse of chrome extension involvement

I have an automation test suite which includes the browser extension loading. I want to run these tests in gitlab but as far as I read, the headless chrome does not support the chrome extensions.
I can't use mozilla firefox as the extension is not supported by firefox. Please suggest me a way so that I can run my tests with the extension in gitlab CI.
Thanks in advance!
While looking for the solutions, I read about xvfb virtual display. I don't know what is it or will it work in gitlab. I tried but it did not work.

VS Code React app closes/crashes using Chrome debugger

I am troubleshooting an issue I am having debugging a React application using VS Code with the Chrome debugger extension. I am using Windows 10 x64.
When I try to log into the application from the app's login page, the debug browser closes without any error (see screenshot below of break-point in code where the browser closes/crashes). I've tried debugging with both Chrome and Edge and I see the same issue with both browsers.
I do not have the same issue running the application without debugger from npm start. Nor do I see the issue when running the application from Chrome debugger on a different computer. Also my friend who is working on the same code does not see the issue on his computer when debugging or running the code.
I cloned an extra copy of the application code onto a different directory on my computer and that did not fix the issue.
I see a file is created \src\debug.log which seems like it could be related to the issue, but not sure what this is used for. The log file just shows the below error over and over.
ERROR:crash_report_database_win.cc(469)] failed to stat report
Any ideas on how I can fix this or what might be happening here?
I faced with the same issue in the Chrome version 85, I've updated to version 86.0.4240.75 and now is working for me
Here you'll find the Chrome Bug Report: https://bugs.chromium.org/p/chromium/issues/detail?id=1123329
The solution for now is to disable the new Javascript Debugger
"debug.javascript.usePreview": false

Firefox React developer tools stopped working

I've been using the React developer tools extension in Firefox for some time, they're great. But yesterday the tools stopped working. The Components tab is available, but it doesn't show any content - my React component tree is simply missing, the pane is blank.
I've tried uninstalling the extension, closing Firefox, and reinstalling the extension.
I've tried rebooting my machine.
I've checked the Components tab settings, everything looks OK.
I've tried reverting to an old version of my project, back when the Developer tools definitely worked.
Has anybody got any ideas? There's no error, and I can't think of any way to investigate what's causing the problem. I haven't found anything by web searching.
And I can't switch to Chrome, because the tools won't install on Chrome under Linux!
OS: Linux mint Cinnamon
Firefox version: 63.0.3 (64 bit)
Phew, got it working again! I'm posting what worked for me in case it helps anybody else.
I completely uninstalled Firefox and reinstalled it following these instructions:
https://www.fosslinux.com/13881/how-to-clean-uninstall-and-reinstall-firefox-in-ubuntu.htm
Then re-added the Developer Tools extension, and it is now working. Firefox is now at version 69.0.

Selenium Jar File 2.44.0

I want to know whether Selenium jar 2.44.0 (new one) supports Firefox 35.0.1 or not. Please suggest.
Getting error :
org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host
As far as I know , Selenium latest version supports till firefox 33.0.
Still I think you should check browser compatibility with selenium versions before start work so please check at below :
Selenium with browser compatibility

E2E Testing in Protractor using Firefox or Safari?

I am using Protractor to test my angular.js app and its working great in Chrome. I had some issues getting it set up and learning the extra webdriver syntax for jasmine, but now I'm getting the hang of it and have a number of tests that are running and passing in Chrome.
Does anyone know of any way to run Protractor in Firefox or Safari or IE or Opera? I'd like to be able to run these tests against more browsers than just Chrome. I've looked through the Protractor docs on GitHub but it only shows config files for the chromeDriver. Is there such thing as a Firefox driver or a Safari driver?
PS. I don't think it'll be much help, so I'm not posting my current config file, but if it is useful, let me know and I can post it here.
Yes! You'll need to do a little setup depending on which browser driver you want to use, but firefox and safari should be trivial. Their drivers are included in the Selenium Standalone server. Just add
capabilities: {
'browserName': 'firefox' // or 'safari'
},
to the config file.
For IE, you need to install a separate binary, and the Selenium Standalone Server needs that binary to be in your PATH. After that, you should be able to use ie as a browsername in your config. Check out the IEDriver documentation here - http://code.google.com/p/selenium/wiki/InternetExplorerDriver

Resources