Specify optional selenium server startup arguments
Reported by Niall Mullally | March 3rd, 2009 @ 05:31 PM
Small patch to allow specifying an array of extra arguments to pass the Selenium remote control when starting up.
This can come in handy for things like specifying a particular Firefox profile to load.
Example:
Webrat.configure do |config| config.selenium_additional_startup_args = ["-firefoxProfileTemplate /path/to/firefox/profile"] end
I've already used this in one project for loading a Firefox
profile that has already accepted my self-signed SSL
certificate.
Without this profile, Selenium was loading a new Firefox profile each time the server ran and the cert exception dialog box would pop up upon the first visit to a HTTPS URL, thus breaking the test(s).
Anyway, I hope this is of use. It's my first ever patch in the open source community so I hope it's up to snuff :-)
Comments and changes to this ticket
-
-
gaffo April 22nd, 2009 @ 02:41 PM
- State changed from “new” to “awaiting-patch”
Sorry that it took so long to get back but this patch no longer cleanly applys to master. Could you please resubmit it. Otherwise this seems completely reasonable.
-
-
Niall Mullally November 26th, 2009 @ 10:34 AM
- Tag changed from “patch, selenium, seleniumsession” to “patch”
Another updated patch attached, if you're interested.
-
Niall Mullally June 8th, 2010 @ 04:17 AM
Yep, that was added in v0.7.1, thanks for pointing it out cschiefelbein.
Unless there's another valid reason to specify selenium server startup options, I think this ticket can now be closed.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Ruby Acceptance Testing for Web applications.
gaffo
Niall Mullally