Question

I’m running Selenium 2.0b4dev on Selenium Grid in Ubuntu 10.04, using Python code to write test cases. I’ve been having trouble with getting basic HTTP authentication to a specific site working, and with a quick google search found that my problem could be solved with the addition of the line self.selenium.add_custom_request_header(“Authorization”, “Basic %s” % _encoded) (with a proper line break in the middle to conform to PEP 8, of course.)

Unfortunately, apparently also through my search I found in order for that line of code to work I need to configure my browser (whichever one I’m using to run the test cases on the grid) to treat Selenium’s (automatically running, apparently?) proxy server as a proxy for that browser to use. But apparently I need to modify the profile of Firefox (or IE)’s launcher to automatically use that proxy, since the whole point of these Selenium Grid test cases is that they aren’t supposed to require user intervention, and I have little to no idea how to do that. I’ve just been using the “ant launch-hub” and “ant launch-remote-control” and then running python programs on the hub that import selenium and unittest.

If anyone could help, that would be just fantastic.

Answer 1

I wrote up an article on how to do this in Ruby. It links to a complementary article on testing self-signed certificates and gives you the set of flags you need to launch Selenium with.

http://mogotest.com/blog/2010/06/23/how-to-perform-basic-auth-in-selenium

To pass args through from grid to the underlying RC server, you need to use something like:


ant -DseleniumArgs="-trustAllSSLCertificates" launch-remote-control


Re: browsers . . . firefox will auto-enable the proxy mode stuff if you pass trustAllSSLCertificates now. Otherwise you need to use *firefoxproxy. IE requires the use of *iexploreproxy or a custom HTA launcher that configures the proxy (the article links to one we open-sourced but would need to be updated to work with 2.0 beta 4).