Posts Tagged ‘selenium server arguments’

Selenium server Arguments.

July 4, 2011 2 comments

Following are the arguments we can use while starting Selenium Server. If we use these arguments properly we can reduce the amount of time spent for finding a solution for complex scenarios.

port <nnnn>: the port number the selenium server should use
(default 4444)

timeout <nnnn>: an integer number of seconds before we should give up

interactive: puts you into interactive mode.  See the tutorial for more details

singleWindow: puts you into a mode where the test web site executes in a frame. This mode should only be selected if the application under test does not use frames.

profilesLocation: Specifies the directory that holds the profiles that java clients can use to start up selenium.  Currently  supported for Firefox only.

forcedBrowserMode <browser>: sets the browser mode to a single  argument (e.g. “*iexplore”) for all sessions, no matter what is passed to getNewBrowserSession

forcedBrowserModeRestOfLine <browser>: sets the browser mode to all the remaining tokens on the line (e.g. “*custom /some/random/place/iexplore.exe”) for all sessions, no matter what is passed to getNewBrowserSession

userExtensions <file>: indicates a JavaScript file that will be loaded into selenium

browserSessionReuse: stops re-initialization and spawning of the browser between tests

avoidProxy: By default, we proxy every browser request; set this flag to make the browser use our proxy only for URLs containing ‘/selenium-server’

firefoxProfileTemplate <dir>: normally, we generate a fresh empty Firefox profile every time we launch.  You can specify a director to make us copy your profile directory instead.

debug: puts you into debug mode, with more trace information anddiagnostics on the console

browserSideLog: enables logging on the browser side; logging messages will be transmitted to the server.  This can affect performance.

ensureCleanSession: If the browser does not have user profiles, make sure every new session has no artifacts from previous  sessions.  For example, enabling this option will cause all user cookies to be archived before launching IE, and restored after IE is closed.

trustAllSSLCertificates: Forces the Selenium proxy to trust all  SSL certificates.  This doesn’t work in browsers that don’t use the  Selenium proxy.

log <logFileName>: writes lots of debug information out to a log  file

htmlSuite <browser> <startURL> <suiteFile> <resultFile>: Run a single HTML Selenese (Selenium Core) suite and then exit immediately, using the specified browser (e.g. “*firefox”) on the specified URL (e.g. “;).  You need to specify the absolute path to the HTML test suite as well as the path to the HTML results file we’ll generate.

proxyInjectionMode: puts you into proxy injection mode, a mode  where the selenium server acts as a proxy server for all content going to the test application.  Under this mode, multiple domains can be visited, and the following additional flags are supported:

dontInjectRegex <regex>: an optional regular expression that proxy injection mode can use to know when to bypss injection

userJsInjection <file>: specifies a JavaScript file which will then be injected into all pages

userContentTransformation <regex> <replacement>: a regular  expression which is matched against all test HTML content; the  second is a string which will replace matches.  These flags can be used any number of times.  A simple example of how this could be useful: if you add “-userContentTransformation https http” then all “https” strings in the HTML of the test application will be changed to be “http”.

%d bloggers like this: