We Keep Coding

Camera usage notification at mozilla firefox

I'm writting an automatied test with using selenium dirver and geckoDriver for mozilla firefox v56. The application which I'm testing always ask user to allow the camera usage and always this notification is displayed:
The problem is that, the Mozilla browser session which is created by geckoDriver does not saved settings where I always allow this page to use the camera driver.
I'm talking about this solution: https://support.mozilla.org/en-US/kb/firefox-page-info-window
I cannot find any parameter in about::config page which which I can run firefox to never ask about this permission again. Can I ask for your help?

Selenium FirefoxDriver initialization

When I am trying to load the Selenium FireFoxDriver, process is taking more time to invoke the browser. I have tried for lot of options like disabling the auto updates and etc. But all efforts are in vain. So I have decided to load the FirefoxDriver on startup of the Server (i.e, with load-on-startup time as 0 in web.xml when container initializes). Are there any cons with this approach? Also please suggest if there is any better way to do this.
Thanks in advance!!!

In general, WebDriver supports Firfox and Safari browsers by default. There is no need to perform any configuration for this. Please find below for the sample code which initializes the browser
WebDriver driver = new FirefoxDriver();
driver.get("http://www.google.com/");
The above code will start the firefox browser installed in your machine and launches the google page. If there is a mismatch between the selenium version of firefox version the browser will be started, but would not launch the google application.
Hope this helps.

What is the mechinism used for commiunication between webdriver and browser

Anyone can explain how communication happen between browser and web-driver?. How does webdriver object read and identify html elements in browser ?. For that what is the relationship between webdriver object and browser and how to build the relationship browser and webdriver object?
driver = new FirefoxDriver();
driver.findElements(By.id("element"));

The communication between webdriver and browser happens through a json-wire protocol which is specified in the W3C documentation. All browsers that webdriver supports, uses this same protocol.
How does webdriver read and identify elements in a page? This varies from browser to browser.
Firefox - webdriver gets installed as a plugin in your browser while running the test. The webdriver server will send the json-commands to this plugin and those commands will get executed in the browser. The plugin is built within the webdriver jar file. It will get installed while running the test.
Chrome - For testing chrome, you would also need a chromedriver.exe file. This chromedriver.exe acts similar to the firefox plugin. It can receive the commands from webdriver server and execute it on the browser
IE - Similar to Chrome, IE executes with the help of InternetExplorerDriver.exe.
You can understand more about the functioning by looking at the different DriverFile source code in github.
You can also get an understanding about the working from here - http://www.aosabook.org/en/selenium.html.
I am not sure how updated this page is, but should help to understand the concept.

Can't upgrade Firefox with selenium

Temporarily I upgrade my sofware for automation web test.
I had Selenium 2.41 and Firefox27 working fine. When I try to upgrade the software, there is no problem about Selenium (I can upgrade to the latest release 2.45 and it's working fine with Firefox27) but I can't upgrade to any Firefox version higher than 29...and this is a problem for us.
I tried to run my test but I get this exception at some point:
"Failed to start new browser session, shutdown browser and clear all session data
org.openqa.selenium.server.RemoteCommandException: timed out waiting for window 'null' to appear"
Any idea?
Best regards and thanks

Disclaimer: I'm using Selenium's .NET bindings, not Java. I don't think that will make a difference in this case.
Selenium 2.44 had an issue with Firefox 36, but this was resolved in Selenium 2.45. It's possible that Firefox versions between 29 and 35 might be incompatible with Selenium 2.45, although this is just a guess on my part.
I had an issue with Seleinum 2.45 driving Firefox version 38: when instantiating the Firefox driver with no profile, an instance of Firefox would load and immediately crash to desktop; subsequently another instance would load as normal.
I found that the issue didn't occur when instantiating the Selenium Firefox driver from an existing profile, so my workaround was to create a blank profile, launch Selenium's Firefox driver using a temporary copy of that profile; then at the conclusion of the test, delete the temporary copy.
Try launching the Firefox driver with an existing profile.

Check Point SSL Network Extender works in FF, not in Safari, on Mountain Lion

I am using Check Point SSL Network Extender on Mac (Mountain Lion) with Java 7 update 40.
It works, i.e. connects to the VPN server (sometimes) in Firefox, but not in Safari.
I would like to be able to get it to work in Safari as I have to run different versions of FF which means I have to start and stop it (and reconnecting is flaky). Please don't ask why I use early versions of FF...
I have found the java logs, but have not found out why the client (applet) fails in Safari. If anyone else has any experience or advice as to an alternative, it would be appreciated...
Thanks

I got it to work in the latest FireFox (26).
I chose Medium Java security setting. Firefox v26 (latest version) connected (after it failed, cleared cache, tried again). First time this has happened.
I reset Java security setting to High, and Firefox v26 still connected.
Hope this can help someone else out!