diff options
Diffstat (limited to 'tests/test_tools/selenium/reference.html')
| -rw-r--r-- | tests/test_tools/selenium/reference.html | 3858 |
1 files changed, 3858 insertions, 0 deletions
diff --git a/tests/test_tools/selenium/reference.html b/tests/test_tools/selenium/reference.html new file mode 100644 index 00000000..5533764a --- /dev/null +++ b/tests/test_tools/selenium/reference.html @@ -0,0 +1,3858 @@ +<html> +<head> +<META http-equiv="Content-Type" content="text/html; charset=UTF-8"> +<title>Selenium Reference</title> +</head> +<body> +<h1>Selenium Reference</h1> +<h2>Concepts</h2> +<p>A <strong>command</strong> is what tells Selenium what to do. Selenium commands come in three 'flavors': <strong>Actions</strong>, <strong>Accessors</strong> and <strong>Assertions</strong>. + Each command call is one line in the test table of the form:</p> +<blockquote> +<table border="1" class="table"> +<colgroup> +<col width="39%"> +<col width="33%"> +<col width="28%"> +</colgroup> +<tbody valign="top"> +<tr> +<td>command</td><td>target</td><td>value</td> +</tr> +</tbody> +</table> +</blockquote> +<p> +<strong>Actions</strong> are commands that generally manipulate the state of the application. They do things like "click this link" and "select that option". If an Action fails, or has an error, the execution of the current test is stopped.</p> +<p>Many Actions can be called with the "AndWait" suffix, e.g. "clickAndWait". + This suffix tells Selenium that the action will cause the browser to make a call to the server, + and that Selenium should wait for a new page to load.</p> +<p> +<strong>Accessors</strong> examine the state of the application and store the results in variables, e.g. "storeTitle". They are also used to automatically generate Assertions.</p> +<p> +<strong>Assertions</strong> are like Accessors, but they verify that the state of the application conforms to what is expected. Examples include "make sure the page title is X" and "verify that this checkbox is checked".</p> +<p>All Selenium Assertions can be used in 3 modes: "assert", "verify", and "waitFor". For example, you can "assertText", "verifyText" and "waitForText". When an "assert" fails, the test is aborted. When a "verify" fails, the test will continue execution, logging the failure. This allows a single "assert" to ensure that the application is on the correct page, followed by a bunch of "verify" assertions to test form field values, labels, etc.</p> +<p>"waitFor" commands wait for some condition to become true (which can be useful for testing Ajax applications). + They will succeed immediately if the condition is already true. + However, they will fail and halt the test if the condition does not become true within the current timeout setting + (see the <strong>setTimeout</strong> action below). + </p> +<p> +<strong>Element Locators</strong> tell Selenium which HTML element a command refers to. Many commands require an Element Locator as the "target" attribute. Examples of Element Locators include "elementId" and "document.forms[0].element". These are described more clearly in the next section.</p> +<p> +<strong>Patterns</strong> are used for various reasons, e.g. to specify the expected value of an input field, or identify a select option. Selenium supports various types of pattern, including regular-expressions, all of which are described in more detail below.</p>Defines an object that runs Selenium commands. + +<h3> +<a name="locators"></a>Element Locators</h3> +<p> +Element Locators tell Selenium which HTML element a command refers to. +The format of a locator is:</p> +<blockquote> +<em>locatorType</em><strong>=</strong><em>argument</em> +</blockquote> +<p> +We support the following strategies for locating elements: +</p> +<blockquote> +<dl> +<dt> +<strong>identifier</strong>=<em>id</em> +</dt> +<dd>Select the element with the specified @id attribute. If no match is +found, select the first element whose @name attribute is <em>id</em>. +(This is normally the default; see below.)</dd> +<dt> +<strong>id</strong>=<em>id</em> +</dt> +<dd>Select the element with the specified @id attribute.</dd> +<dt> +<strong>name</strong>=<em>name</em> +</dt> +<dd>Select the first element with the specified @name attribute.</dd> +<dd> +<ul class="first last simple"> +<li>username</li> +<li>name=username</li> +</ul> +</dd> +<dd>The name may optionally be followed by one or more <em>element-filters</em>, separated from the name by whitespace. If the <em>filterType</em> is not specified, <strong>value</strong> is assumed.</dd> +<dd> +<ul class="first last simple"> +<li>name=flavour value=chocolate</li> +</ul> +</dd> +<dt> +<strong>dom</strong>=<em>javascriptExpression</em> +</dt> +<dd> +<dd>Find an element using JavaScript traversal of the HTML Document Object +Model. DOM locators <em>must</em> begin with "document.". +<ul class="first last simple"> +<li>dom=document.forms['myForm'].myDropdown</li> +<li>dom=document.images[56]</li> +</ul> +</dd> +</dd> +<dt> +<strong>xpath</strong>=<em>xpathExpression</em> +</dt> +<dd>Locate an element using an XPath expression. +<ul class="first last simple"> +<li>xpath=//img[@alt='The image alt text']</li> +<li>xpath=//table[@id='table1']//tr[4]/td[2]</li> +</ul> +</dd> +<dt> +<strong>link</strong>=<em>textPattern</em> +</dt> +<dd>Select the link (anchor) element which contains text matching the +specified <em>pattern</em>. +<ul class="first last simple"> +<li>link=The link text</li> +</ul> +</dd> +<dt> +<strong>css</strong>=<em>cssSelectorSyntax</em> +</dt> +<dd>Select the element using css selectors. Please refer to <a href="http://www.w3.org/TR/REC-CSS2/selector.html">CSS2 selectors</a>, <a href="http://www.w3.org/TR/2001/CR-css3-selectors-20011113/">CSS3 selectors</a> for more information. You can also check the TestCssLocators test in the selenium test suite for an example of usage, which is included in the downloaded selenium core package. +<ul class="first last simple"> +<li>css=a[href="#id3"]</li> +<li>css=span#firstChild + span</li> +</ul> +</dd> +<dd>Currently the css selector locator supports all css1, css2 and css3 selectors except namespace in css3, some pseudo classes(:nth-of-type, :nth-last-of-type, :first-of-type, :last-of-type, :only-of-type, :visited, :hover, :active, :focus, :indeterminate) and pseudo elements(::first-line, ::first-letter, ::selection, ::before, ::after). </dd> +</dl> +</blockquote> +<p> +Without an explicit locator prefix, Selenium uses the following default +strategies: +</p> +<ul class="simple"> +<li> +<strong>dom</strong>, for locators starting with "document."</li> +<li> +<strong>xpath</strong>, for locators starting with "//"</li> +<li> +<strong>identifier</strong>, otherwise</li> +</ul> +<h3> +<a name="element-filters">Element Filters</a> +</h3> +<blockquote> +<p>Element filters can be used with a locator to refine a list of candidate elements. They are currently used only in the 'name' element-locator.</p> +<p>Filters look much like locators, ie.</p> +<blockquote> +<em>filterType</em><strong>=</strong><em>argument</em> +</blockquote> +<p>Supported element-filters are:</p> +<p> +<strong>value=</strong><em>valuePattern</em> +</p> +<blockquote> +Matches elements based on their values. This is particularly useful for refining a list of similarly-named toggle-buttons.</blockquote> +<p> +<strong>index=</strong><em>index</em> +</p> +<blockquote> +Selects a single element based on its position in the list (offset from zero).</blockquote> +</blockquote> +<h3> +<a name="patterns"></a>String-match Patterns</h3> +<p> +Various Pattern syntaxes are available for matching string values: +</p> +<blockquote> +<dl> +<dt> +<strong>glob:</strong><em>pattern</em> +</dt> +<dd>Match a string against a "glob" (aka "wildmat") pattern. "Glob" is a +kind of limited regular-expression syntax typically used in command-line +shells. In a glob pattern, "*" represents any sequence of characters, and "?" +represents any single character. Glob patterns match against the entire +string.</dd> +<dt> +<strong>regexp:</strong><em>regexp</em> +</dt> +<dd>Match a string using a regular-expression. The full power of JavaScript +regular-expressions is available.</dd> +<dt> +<strong>exact:</strong><em>string</em> +</dt> +<dd>Match a string exactly, verbatim, without any of that fancy wildcard +stuff.</dd> +</dl> +</blockquote> +<p> +If no pattern prefix is specified, Selenium assumes that it's a "glob" +pattern. +</p> +<h2>Selenium Actions</h2> +<dl> +<dt> +<strong><a name="addSelection"></a>addSelection + ( + locator,optionLocator + ) + </strong> +</dt> +<dd>Add a selection to the set of selected options in a multi-select element using an option locator. + +@see #doSelect for details of option locators<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> identifying a multi-select box</li> +<li>optionLocator - an option locator (a label by default)</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="answerOnNextPrompt"></a>answerOnNextPrompt + ( + answer + ) + </strong> +</dt> +<dd>Instructs Selenium to return the specified answer string in response to +the next JavaScript prompt [window.prompt()].<p>Arguments:</p> +<ul> +<li>answer - the answer to give in response to the prompt pop-up</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="check"></a>check + ( + locator + ) + </strong> +</dt> +<dd>Check a toggle-button (checkbox/radio)<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="chooseCancelOnNextConfirmation"></a>chooseCancelOnNextConfirmation + ( + + ) + </strong> +</dt> +<dd>By default, Selenium's overridden window.confirm() function will +return true, as if the user had manually clicked OK. After running +this command, the next call to confirm() will return false, as if +the user had clicked Cancel.</dd> +<br> +<dt> +<strong><a name="click"></a>click + ( + locator + ) + </strong> +</dt> +<dd>Clicks on a link, button, checkbox or radio button. If the click action +causes a new page to load (like a link usually does), call +waitForPageToLoad.<p>Arguments:</p> +<ul> +<li>locator - an element locator</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="clickAt"></a>clickAt + ( + locator,coordString + ) + </strong> +</dt> +<dd>Clicks on a link, button, checkbox or radio button. If the click action +causes a new page to load (like a link usually does), call +waitForPageToLoad. + +Beware of http://jira.openqa.org/browse/SEL-280, which will lead some event handlers to +get null event arguments. Read the bug for more details, including a workaround.<p>Arguments:</p> +<ul> +<li>locator - an element locator</li> +<li>coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="close"></a>close + ( + + ) + </strong> +</dt> +<dd>Simulates the user clicking the "close" button in the titlebar of a popup +window or tab.</dd> +<br> +<dt> +<strong><a name="createCookie"></a>createCookie + ( + nameValuePair,optionsString + ) + </strong> +</dt> +<dd>Create a new cookie whose path and domain are same with those of current page +under test, unless you specified a path for this cookie explicitly.<p>Arguments:</p> +<ul> +<li>nameValuePair - name and value of the cookie in a format "name=value"</li> +<li>optionsString - options for the cookie. Currently supported options include 'path' and 'max_age'. the optionsString's format is "path=/path/, max_age=60". The order of options are irrelevant, the unit of the value of 'max_age' is second.</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="deleteCookie"></a>deleteCookie + ( + name,path + ) + </strong> +</dt> +<dd>Delete a named cookie with specified path.<p>Arguments:</p> +<ul> +<li>name - the name of the cookie to be deleted</li> +<li>path - the path property of the cookie to be deleted</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="dragdrop"></a>dragdrop + ( + locator,movementsString + ) + </strong> +</dt> +<dd>Drags an element a certain distance and then drops it +Beware of http://jira.openqa.org/browse/SEL-280, which will lead some event handlers to +get null event arguments. Read the bug for more details, including a workaround.<p>Arguments:</p> +<ul> +<li>locator - an element locator</li> +<li>movementsString - offset in pixels from the current location to which the element should be moved, e.g., "+70,-300"</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="fireEvent"></a>fireEvent + ( + locator,eventName + ) + </strong> +</dt> +<dd>Explicitly simulate an event, to trigger the corresponding "on<em>event</em>" +handler.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>eventName - the event name, e.g. "focus" or "blur"</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="goBack"></a>goBack + ( + + ) + </strong> +</dt> +<dd>Simulates the user clicking the "back" button on their browser.</dd> +<br> +<dt> +<strong><a name="keyDown"></a>keyDown + ( + locator,keySequence + ) + </strong> +</dt> +<dd>Simulates a user pressing a key (without releasing it yet).<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>keySequence - Either be a string("\" followed by the numeric keycode of the key to be pressed, normally the ASCII value of that key), or a single character. For example: "w", "\119".</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="keyPress"></a>keyPress + ( + locator,keySequence + ) + </strong> +</dt> +<dd>Simulates a user pressing and releasing a key.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>keySequence - Either be a string("\" followed by the numeric keycode of the key to be pressed, normally the ASCII value of that key), or a single character. For example: "w", "\119".</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="keyUp"></a>keyUp + ( + locator,keySequence + ) + </strong> +</dt> +<dd>Simulates a user releasing a key.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>keySequence - Either be a string("\" followed by the numeric keycode of the key to be pressed, normally the ASCII value of that key), or a single character. For example: "w", "\119".</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseDown"></a>mouseDown + ( + locator + ) + </strong> +</dt> +<dd>Simulates a user pressing the mouse button (without releasing it yet) on +the specified element.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseDownAt"></a>mouseDownAt + ( + locator,coordString + ) + </strong> +</dt> +<dd>Simulates a user pressing the mouse button (without releasing it yet) on +the specified element. + +Beware of http://jira.openqa.org/browse/SEL-280, which will lead some event handlers to +get null event arguments. Read the bug for more details, including a workaround.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseMove"></a>mouseMove + ( + locator + ) + </strong> +</dt> +<dd>Simulates a user pressing the mouse button (without releasing it yet) on +the specified element.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseMoveAt"></a>mouseMoveAt + ( + locator,coordString + ) + </strong> +</dt> +<dd>Simulates a user pressing the mouse button (without releasing it yet) on +the specified element. + +Beware of http://jira.openqa.org/browse/SEL-280, which will lead some event handlers to +get null event arguments. Read the bug for more details, including a workaround.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseOut"></a>mouseOut + ( + locator + ) + </strong> +</dt> +<dd>Simulates a user moving the mouse pointer away from the specified element.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseOver"></a>mouseOver + ( + locator + ) + </strong> +</dt> +<dd>Simulates a user hovering a mouse over the specified element.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseUp"></a>mouseUp + ( + locator + ) + </strong> +</dt> +<dd>Simulates a user pressing the mouse button (without releasing it yet) on +the specified element.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="mouseUpAt"></a>mouseUpAt + ( + locator,coordString + ) + </strong> +</dt> +<dd>Simulates a user pressing the mouse button (without releasing it yet) on +the specified element. + +Beware of http://jira.openqa.org/browse/SEL-280, which will lead some event handlers to +get null event arguments. Read the bug for more details, including a workaround.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="open"></a>open + ( + url + ) + </strong> +</dt> +<dd>Opens an URL in the test frame. This accepts both relative and absolute +URLs. + +The "open" command waits for the page to load before proceeding, +ie. the "AndWait" suffix is implicit. + +<em>Note</em>: The URL must be on the same domain as the runner HTML +due to security restrictions in the browser (Same Origin Policy). If you +need to open an URL on another domain, use the Selenium Server to start a +new browser session on that domain.<p>Arguments:</p> +<ul> +<li>url - the URL to open; may be relative or absolute</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="refresh"></a>refresh + ( + + ) + </strong> +</dt> +<dd>Simulates the user clicking the "Refresh" button on their browser.</dd> +<br> +<dt> +<strong><a name="removeSelection"></a>removeSelection + ( + locator,optionLocator + ) + </strong> +</dt> +<dd>Remove a selection from the set of selected options in a multi-select element using an option locator. + +@see #doSelect for details of option locators<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> identifying a multi-select box</li> +<li>optionLocator - an option locator (a label by default)</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="select"></a>select + ( + selectLocator,optionLocator + ) + </strong> +</dt> +<dd>Select an option from a drop-down using an option locator. + +<p> +Option locators provide different ways of specifying options of an HTML +Select element (e.g. for selecting a specific option, or for asserting +that the selected option satisfies a specification). There are several +forms of Select Option Locator. +</p> +<dl> +<dt> +<strong>label</strong>=<em>labelPattern</em> +</dt> +<dd>matches options based on their labels, i.e. the visible text. (This +is the default.) +<ul class="first last simple"> +<li>label=regexp:^[Oo]ther</li> +</ul> +</dd> +<dt> +<strong>value</strong>=<em>valuePattern</em> +</dt> +<dd>matches options based on their values. +<ul class="first last simple"> +<li>value=other</li> +</ul> +</dd> +<dt> +<strong>id</strong>=<em>id</em> +</dt> +<dd>matches options based on their ids. +<ul class="first last simple"> +<li>id=option1</li> +</ul> +</dd> +<dt> +<strong>index</strong>=<em>index</em> +</dt> +<dd>matches an option based on its index (offset from zero). +<ul class="first last simple"> +<li>index=2</li> +</ul> +</dd> +</dl> +<p> +If no option locator prefix is provided, the default behaviour is to match on <strong>label</strong>. +</p> +<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>optionLocator - an option locator (a label by default)</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="selectFrame"></a>selectFrame + ( + locator + ) + </strong> +</dt> +<dd>Selects a frame within the current window. (You may invoke this command +multiple times to select nested frames.) To select the parent frame, use +"relative=parent" as a locator; to select the top frame, use "relative=top". + +<p>You may also use a DOM expression to identify the frame you want directly, +like this: <code>dom=frames["main"].frames["subframe"]</code> +</p> +<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> identifying a frame or iframe</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="selectWindow"></a>selectWindow + ( + windowID + ) + </strong> +</dt> +<dd>Selects a popup window; once a popup window has been selected, all +commands go to that window. To select the main window again, use "null" +as the target.<p>Arguments:</p> +<ul> +<li>windowID - the JavaScript window ID of the window to select</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="setContext"></a>setContext + ( + context,logLevelThreshold + ) + </strong> +</dt> +<dd>Writes a message to the status bar and adds a note to the browser-side +log. + +<p>If logLevelThreshold is specified, set the threshold for logging +to that level (debug, info, warn, error).</p> +<p>(Note that the browser-side logs will <i>not</i> be sent back to the +server, and are invisible to the Client Driver.)</p> +<p>Arguments:</p> +<ul> +<li>context - the message to be sent to the browser</li> +<li>logLevelThreshold - one of "debug", "info", "warn", "error", sets the threshold for browser-side logging</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="setCursorPosition"></a>setCursorPosition + ( + locator,position + ) + </strong> +</dt> +<dd>Moves the text cursor to the specified position in the given input element or textarea. +This method will fail if the specified element isn't an input element or textarea.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to an input element or textarea</li> +<li>position - the numerical position of the cursor in the field; position should be 0 to move the position to the beginning of the field. You can also set the cursor to -1 to move it to the end of the field.</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="setTimeout"></a>setTimeout + ( + timeout + ) + </strong> +</dt> +<dd>Specifies the amount of time that Selenium will wait for actions to complete. + +<p>Actions that require waiting include "open" and the "waitFor*" actions.</p> +The default timeout is 30 seconds.<p>Arguments:</p> +<ul> +<li>timeout - a timeout in milliseconds, after which the action will return with an error</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="submit"></a>submit + ( + formLocator + ) + </strong> +</dt> +<dd>Submit the specified form. This is particularly useful for forms without +submit buttons, e.g. single-input "Search" forms.<p>Arguments:</p> +<ul> +<li>formLocator - an <a href="#locators">element locator</a> for the form you want to submit</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="type"></a>type + ( + locator,value + ) + </strong> +</dt> +<dd>Sets the value of an input field, as though you typed it in. + +<p>Can also be used to set the value of combo boxes, check boxes, etc. In these cases, +value should be the value of the option selected, not the visible text.</p> +<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>value - the value to type</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="uncheck"></a>uncheck + ( + locator + ) + </strong> +</dt> +<dd>Uncheck a toggle-button (checkbox/radio)<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="waitForCondition"></a>waitForCondition + ( + script,timeout + ) + </strong> +</dt> +<dd>Runs the specified JavaScript snippet repeatedly until it evaluates to "true". +The snippet may have multiple lines, but only the result of the last line +will be considered. + +<p>Note that, by default, the snippet will be run in the runner's test window, not in the window +of your application. To get the window of your application, you can use +the JavaScript snippet <code>selenium.browserbot.getCurrentWindow()</code>, and then +run your JavaScript in there</p> +<p>Arguments:</p> +<ul> +<li>script - the JavaScript snippet to run</li> +<li>timeout - a timeout in milliseconds, after which this command will return with an error</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="waitForPageToLoad"></a>waitForPageToLoad + ( + timeout + ) + </strong> +</dt> +<dd>Waits for a new page to load. + +<p>You can use this command instead of the "AndWait" suffixes, "clickAndWait", "selectAndWait", "typeAndWait" etc. +(which are only available in the JS API).</p> +<p>Selenium constantly keeps track of new pages loading, and sets a "newPageLoaded" +flag when it first notices a page load. Running any other Selenium command after +turns the flag to false. Hence, if you want to wait for a page to load, you must +wait immediately after a Selenium command that caused a page-load.</p> +<p>Arguments:</p> +<ul> +<li>timeout - a timeout in milliseconds, after which this command will return with an error</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="waitForPopUp"></a>waitForPopUp + ( + windowID,timeout + ) + </strong> +</dt> +<dd>Waits for a popup window to appear and load up.<p>Arguments:</p> +<ul> +<li>windowID - the JavaScript window ID of the window that will appear</li> +<li>timeout - a timeout in milliseconds, after which the action will return with an error</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="windowFocus"></a>windowFocus + ( + windowName + ) + </strong> +</dt> +<dd>Gives focus to a window<p>Arguments:</p> +<ul> +<li>windowName - name of the window to be given focus</li> +</ul> +</dd> +<br> +<dt> +<strong><a name="windowMaximize"></a>windowMaximize + ( + windowName + ) + </strong> +</dt> +<dd>Resize window to take up the entire screen<p>Arguments:</p> +<ul> +<li>windowName - name of the window to be enlarged</li> +</ul> +</dd> +<br> +</dl> +<h2>Selenium Accessors</h2> +<dl> +<dt> +<strong><a name="storeAlert"></a>storeAlert + + ( + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the message of a JavaScript alert generated during the previous action, or fail if there were no alerts. + +<p>Getting an alert has the same effect as manually clicking OK. If an +alert is generated but you do not get/verify it, the next Selenium action +will fail.</p> +<p>NOTE: under Selenium, JavaScript alerts will NOT pop up a visible alert +dialog.</p> +<p>NOTE: Selenium does NOT support JavaScript alerts that are generated in a +page's onload() event handler. In this case a visible dialog WILL be +generated and Selenium will hang until someone manually clicks OK.</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>The message of the most recent JavaScript alert</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAlert + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAlert + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAlert + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAlert + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAlert + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAlert + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAllButtons"></a>storeAllButtons + + ( + + variableName + ) + + </strong> +</dt> +<dd>Returns the IDs of all buttons on the page. + +<p>If a given button has no ID, it will appear as "" in this array.</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>the IDs of all buttons on the page</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAllButtons + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAllButtons + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAllButtons + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAllButtons + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAllButtons + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAllButtons + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAllFields"></a>storeAllFields + + ( + + variableName + ) + + </strong> +</dt> +<dd>Returns the IDs of all input fields on the page. + +<p>If a given field has no ID, it will appear as "" in this array.</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>the IDs of all field on the page</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAllFields + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAllFields + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAllFields + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAllFields + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAllFields + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAllFields + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAllLinks"></a>storeAllLinks + + ( + + variableName + ) + + </strong> +</dt> +<dd>Returns the IDs of all links on the page. + +<p>If a given link has no ID, it will appear as "" in this array.</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>the IDs of all links on the page</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAllLinks + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAllLinks + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAllLinks + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAllLinks + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAllLinks + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAllLinks + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAllWindowIds"></a>storeAllWindowIds + + ( + + variableName + ) + + </strong> +</dt> +<dd>Returns the IDs of all windows that the browser knows about.<p> +<dl> +<dt>Returns: </dt> +<dd>the IDs of all windows that the browser knows about.</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAllWindowIds + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAllWindowIds + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAllWindowIds + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAllWindowIds + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAllWindowIds + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAllWindowIds + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAllWindowNames"></a>storeAllWindowNames + + ( + + variableName + ) + + </strong> +</dt> +<dd>Returns the names of all windows that the browser knows about.<p> +<dl> +<dt>Returns: </dt> +<dd>the names of all windows that the browser knows about.</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAllWindowNames + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAllWindowNames + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAllWindowNames + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAllWindowNames + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAllWindowNames + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAllWindowNames + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAllWindowTitles"></a>storeAllWindowTitles + + ( + + variableName + ) + + </strong> +</dt> +<dd>Returns the titles of all windows that the browser knows about.<p> +<dl> +<dt>Returns: </dt> +<dd>the titles of all windows that the browser knows about.</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAllWindowTitles + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAllWindowTitles + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAllWindowTitles + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAllWindowTitles + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAllWindowTitles + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAllWindowTitles + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAttribute"></a>storeAttribute + + ( + attributeLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets the value of an element attribute. + +Beware of http://jira.openqa.org/browse/SEL-280, which will lead some event handlers to +get null event arguments. Read the bug for more details, including a workaround.<p>Arguments:</p> +<ul> +<li>attributeLocator - an element locator followed by an</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the value of the specified attribute</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAttribute + ( + attributeLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAttribute + ( + attributeLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAttribute + ( + attributeLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAttribute + ( + attributeLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAttribute + ( + attributeLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAttribute + ( + attributeLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAttributeFromAllWindows"></a>storeAttributeFromAllWindows + + ( + attributeName, + + variableName + ) + + </strong> +</dt> +<dd>Returns every instance of some attribute from all known windows.<p>Arguments:</p> +<ul> +<li>attributeName - name of an attribute on the windows</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the set of values of this attribute from all known windows.</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAttributeFromAllWindows + ( + attributeName, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotAttributeFromAllWindows + ( + attributeName, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyAttributeFromAllWindows + ( + attributeName, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotAttributeFromAllWindows + ( + attributeName, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForAttributeFromAllWindows + ( + attributeName, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotAttributeFromAllWindows + ( + attributeName, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeBodyText"></a>storeBodyText + + ( + + variableName + ) + + </strong> +</dt> +<dd>Gets the entire text of the page.<p> +<dl> +<dt>Returns: </dt> +<dd>the entire text of the page</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertBodyText + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotBodyText + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyBodyText + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotBodyText + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForBodyText + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotBodyText + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeConfirmation"></a>storeConfirmation + + ( + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the message of a JavaScript confirmation dialog generated during +the previous action. + +<p> +By default, the confirm function will return true, having the same effect +as manually clicking OK. This can be changed by prior execution of the +chooseCancelOnNextConfirmation command. If an confirmation is generated +but you do not get/verify it, the next Selenium action will fail. +</p> +<p> +NOTE: under Selenium, JavaScript confirmations will NOT pop up a visible +dialog. +</p> +<p> +NOTE: Selenium does NOT support JavaScript confirmations that are +generated in a page's onload() event handler. In this case a visible +dialog WILL be generated and Selenium will hang until you manually click +OK. +</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>the message of the most recent JavaScript confirmation dialog</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertConfirmation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotConfirmation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyConfirmation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotConfirmation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForConfirmation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotConfirmation + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeCookie"></a>storeCookie + + ( + + variableName + ) + + </strong> +</dt> +<dd>Return all cookies of the current page under test.<p> +<dl> +<dt>Returns: </dt> +<dd>all cookies of the current page under test</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertCookie + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotCookie + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyCookie + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotCookie + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForCookie + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotCookie + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeCursorPosition"></a>storeCursorPosition + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the text cursor position in the given input element or textarea; beware, this may not work perfectly on all browsers. + +<p>Specifically, if the cursor/selection has been cleared by JavaScript, this command will tend to +return the position of the last location of the cursor, even though the cursor is now gone from the page. This is filed as <a href="http://jira.openqa.org/browse/SEL-243">SEL-243</a>.</p> +This method will fail if the specified element isn't an input element or textarea, or there is no cursor in the element.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to an input element or textarea</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the numerical position of the cursor in the field</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertCursorPosition + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotCursorPosition + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyCursorPosition + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotCursorPosition + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForCursorPosition + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotCursorPosition + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeElementHeight"></a>storeElementHeight + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the height of an element<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to an element</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>height of an element in pixels</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertElementHeight + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotElementHeight + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyElementHeight + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotElementHeight + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForElementHeight + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotElementHeight + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeElementIndex"></a>storeElementIndex + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Get the relative index of an element to its parent (starting from 0). The comment node and empty text node +will be ignored.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to an element</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>of relative index of the element to its parent (starting from 0)</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertElementIndex + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotElementIndex + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyElementIndex + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotElementIndex + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForElementIndex + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotElementIndex + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeElementPositionLeft"></a>storeElementPositionLeft + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the horizontal position of an element<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to an element OR an element itself</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>of pixels from the edge of the frame.</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertElementPositionLeft + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotElementPositionLeft + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyElementPositionLeft + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotElementPositionLeft + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForElementPositionLeft + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotElementPositionLeft + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeElementPositionTop"></a>storeElementPositionTop + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the vertical position of an element<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to an element OR an element itself</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>of pixels from the edge of the frame.</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertElementPositionTop + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotElementPositionTop + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyElementPositionTop + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotElementPositionTop + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForElementPositionTop + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotElementPositionTop + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeElementWidth"></a>storeElementWidth + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the width of an element<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to an element</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>width of an element in pixels</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertElementWidth + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotElementWidth + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyElementWidth + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotElementWidth + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForElementWidth + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotElementWidth + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeEval"></a>storeEval + + ( + script, + + variableName + ) + + </strong> +</dt> +<dd>Gets the result of evaluating the specified JavaScript snippet. The snippet may +have multiple lines, but only the result of the last line will be returned. + +<p>Note that, by default, the snippet will run in the context of the "selenium" +object itself, so <code>this</code> will refer to the Selenium object, and <code>window</code> will +refer to the top-level runner test window, not the window of your application.</p> +<p>If you need a reference to the window of your application, you can refer +to <code>this.browserbot.getCurrentWindow()</code> and if you need to use +a locator to refer to a single element in your application page, you can +use <code>this.page().findElement("foo")</code> where "foo" is your locator.</p> +<p>Arguments:</p> +<ul> +<li>script - the JavaScript snippet to run</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the results of evaluating the snippet</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertEval + ( + script, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotEval + ( + script, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyEval + ( + script, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotEval + ( + script, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForEval + ( + script, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotEval + ( + script, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeExpression"></a>storeExpression + + ( + expression, + + variableName + ) + + </strong> +</dt> +<dd>Returns the specified expression. + +<p>This is useful because of JavaScript preprocessing. +It is used to generate commands like assertExpression and waitForExpression.</p> +<p>Arguments:</p> +<ul> +<li>expression - the value to return</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the value passed in</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertExpression + ( + expression, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotExpression + ( + expression, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyExpression + ( + expression, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotExpression + ( + expression, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForExpression + ( + expression, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotExpression + ( + expression, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeHtmlSource"></a>storeHtmlSource + + ( + + variableName + ) + + </strong> +</dt> +<dd>Returns the entire HTML source between the opening and +closing "html" tags.<p> +<dl> +<dt>Returns: </dt> +<dd>the entire HTML source</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertHtmlSource + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotHtmlSource + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyHtmlSource + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotHtmlSource + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForHtmlSource + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotHtmlSource + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeLocation"></a>storeLocation + + ( + + variableName + ) + + </strong> +</dt> +<dd>Gets the absolute URL of the current page.<p> +<dl> +<dt>Returns: </dt> +<dd>the absolute URL of the current page</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertLocation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotLocation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyLocation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotLocation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForLocation + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotLocation + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeLogMessages"></a>storeLogMessages + + ( + + variableName + ) + + </strong> +</dt> +<dd>Return the contents of the log. + +<p>This is a placeholder intended to make the code generator make this API +available to clients. The selenium server will intercept this call, however, +and return its recordkeeping of log messages since the last call to this API. +Thus this code in JavaScript will never be called.</p> +<p>The reason I opted for a servercentric solution is to be able to support +multiple frames served from different domains, which would break a +centralized JavaScript logging mechanism under some conditions.</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>all log messages seen since the last call to this API</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertLogMessages + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotLogMessages + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyLogMessages + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotLogMessages + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForLogMessages + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotLogMessages + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storePrompt"></a>storePrompt + + ( + + variableName + ) + + </strong> +</dt> +<dd>Retrieves the message of a JavaScript question prompt dialog generated during +the previous action. + +<p>Successful handling of the prompt requires prior execution of the +answerOnNextPrompt command. If a prompt is generated but you +do not get/verify it, the next Selenium action will fail.</p> +<p>NOTE: under Selenium, JavaScript prompts will NOT pop up a visible +dialog.</p> +<p>NOTE: Selenium does NOT support JavaScript prompts that are generated in a +page's onload() event handler. In this case a visible dialog WILL be +generated and Selenium will hang until someone manually clicks OK.</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>the message of the most recent JavaScript question prompt</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertPrompt + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotPrompt + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyPrompt + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotPrompt + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForPrompt + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotPrompt + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedId"></a>storeSelectedId + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets option element ID for selected option in the specified select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the selected option ID in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedId + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedId + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedId + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedId + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedId + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedId + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedIds"></a>storeSelectedIds + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets all option element IDs for selected options in the specified select or multi-select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>an array of all selected option IDs in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedIds + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedIds + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedIds + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedIds + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedIds + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedIds + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedIndex"></a>storeSelectedIndex + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets option index (option number, starting at 0) for selected option in the specified select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the selected option index in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedIndex + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedIndex + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedIndex + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedIndex + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedIndex + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedIndex + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedIndexes"></a>storeSelectedIndexes + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets all option indexes (option number, starting at 0) for selected options in the specified select or multi-select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>an array of all selected option indexes in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedIndexes + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedIndexes + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedIndexes + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedIndexes + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedIndexes + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedIndexes + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedLabel"></a>storeSelectedLabel + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets option label (visible text) for selected option in the specified select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the selected option label in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedLabel + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedLabel + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedLabel + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedLabel + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedLabel + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedLabel + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedLabels"></a>storeSelectedLabels + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets all option labels (visible text) for selected options in the specified select or multi-select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>an array of all selected option labels in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedLabels + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedLabels + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedLabels + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedLabels + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedLabels + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedLabels + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedValue"></a>storeSelectedValue + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets option value (value attribute) for selected option in the specified select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the selected option value in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedValue + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedValue + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedValue + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedValue + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedValue + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedValue + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectedValues"></a>storeSelectedValues + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets all option values (value attributes) for selected options in the specified select or multi-select element.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>an array of all selected option values in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectedValues + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectedValues + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectedValues + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectedValues + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectedValues + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectedValues + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSelectOptions"></a>storeSelectOptions + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Gets all option labels in the specified select drop-down.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>an array of all option labels in the specified select drop-down</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSelectOptions + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotSelectOptions + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifySelectOptions + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotSelectOptions + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForSelectOptions + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotSelectOptions + ( + selectLocator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeTable"></a>storeTable + + ( + tableCellAddress, + + variableName + ) + + </strong> +</dt> +<dd>Gets the text from a cell of a table. The cellAddress syntax +tableLocator.row.column, where row and column start at 0.<p>Arguments:</p> +<ul> +<li>tableCellAddress - a cell address, e.g. "foo.1.4"</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the text from the specified cell</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertTable + ( + tableCellAddress, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotTable + ( + tableCellAddress, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyTable + ( + tableCellAddress, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotTable + ( + tableCellAddress, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForTable + ( + tableCellAddress, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotTable + ( + tableCellAddress, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeText"></a>storeText + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Gets the text of an element. This works for any element that contains +text. This command uses either the textContent (Mozilla-like browsers) or +the innerText (IE-like browsers) of the element, which is the rendered +text shown to the user.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the text of the element</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertText + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotText + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyText + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotText + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForText + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotText + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeTitle"></a>storeTitle + + ( + + variableName + ) + + </strong> +</dt> +<dd>Gets the title of the current page.<p> +<dl> +<dt>Returns: </dt> +<dd>the title of the current page</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertTitle + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotTitle + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyTitle + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotTitle + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForTitle + ( + <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotTitle + ( + <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeValue"></a>storeValue + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Gets the (whitespace-trimmed) value of an input field (or anything else with a value parameter). +For checkbox/radio elements, the value will be "on" or "off" depending on +whether the element is checked or not.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>the element value, or "on/off" for checkbox/radio elements</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertValue + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>assertNotValue + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyValue + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>verifyNotValue + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForValue + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +<li>waitForNotValue + ( + locator, <a href="#patterns">pattern</a> + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeWhetherThisFrameMatchFrameExpression"></a>storeWhetherThisFrameMatchFrameExpression + + ( + currentFrameString, +target, + + variableName + ) + + </strong> +</dt> +<dd>Determine whether current/locator identify the frame containing this running code. + +<p>This is useful in proxy injection mode, where this code runs in every +browser frame and window, and sometimes the selenium server needs to identify +the "current" frame. In this case, when the test calls selectFrame, this +routine is called for each frame to figure out which one has been selected. +The selected frame will return true, while all others will return false.</p> +<p>Arguments:</p> +<ul> +<li>currentFrameString - starting frame</li> +<li>target - new frame (which might be relative to the current one)</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if the new frame is this code's window</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertWhetherThisFrameMatchFrameExpression + ( + currentFrameString, target + ) + </li> +<li>assertNotWhetherThisFrameMatchFrameExpression + ( + currentFrameString, target + ) + </li> +<li>verifyWhetherThisFrameMatchFrameExpression + ( + currentFrameString, target + ) + </li> +<li>verifyNotWhetherThisFrameMatchFrameExpression + ( + currentFrameString, target + ) + </li> +<li>waitForWhetherThisFrameMatchFrameExpression + ( + currentFrameString, target + ) + </li> +<li>waitForNotWhetherThisFrameMatchFrameExpression + ( + currentFrameString, target + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeAlertPresent"></a>storeAlertPresent + + ( + + variableName + ) + + </strong> +</dt> +<dd>Has an alert occurred? + +<p> +This function never throws an exception +</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if there is an alert</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertAlertPresent + ( + + ) + </li> +<li>assertAlertNotPresent + ( + + ) + </li> +<li>verifyAlertPresent + ( + + ) + </li> +<li>verifyAlertNotPresent + ( + + ) + </li> +<li>waitForAlertPresent + ( + + ) + </li> +<li>waitForAlertNotPresent + ( + + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeChecked"></a>storeChecked + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Gets whether a toggle-button (checkbox/radio) is checked. Fails if the specified element doesn't exist or isn't a toggle-button.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> pointing to a checkbox or radio button</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if the checkbox is checked, false otherwise</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertChecked + ( + locator + ) + </li> +<li>assertNotChecked + ( + locator + ) + </li> +<li>verifyChecked + ( + locator + ) + </li> +<li>verifyNotChecked + ( + locator + ) + </li> +<li>waitForChecked + ( + locator + ) + </li> +<li>waitForNotChecked + ( + locator + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeConfirmationPresent"></a>storeConfirmationPresent + + ( + + variableName + ) + + </strong> +</dt> +<dd>Has confirm() been called? + +<p> +This function never throws an exception +</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if there is a pending confirmation</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertConfirmationPresent + ( + + ) + </li> +<li>assertConfirmationNotPresent + ( + + ) + </li> +<li>verifyConfirmationPresent + ( + + ) + </li> +<li>verifyConfirmationNotPresent + ( + + ) + </li> +<li>waitForConfirmationPresent + ( + + ) + </li> +<li>waitForConfirmationNotPresent + ( + + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeEditable"></a>storeEditable + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Determines whether the specified input element is editable, ie hasn't been disabled. +This method will fail if the specified element isn't an input element.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if the input element is editable, false otherwise</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertEditable + ( + locator + ) + </li> +<li>assertNotEditable + ( + locator + ) + </li> +<li>verifyEditable + ( + locator + ) + </li> +<li>verifyNotEditable + ( + locator + ) + </li> +<li>waitForEditable + ( + locator + ) + </li> +<li>waitForNotEditable + ( + locator + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeElementPresent"></a>storeElementPresent + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Verifies that the specified element is somewhere on the page.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if the element is present, false otherwise</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertElementPresent + ( + locator + ) + </li> +<li>assertElementNotPresent + ( + locator + ) + </li> +<li>verifyElementPresent + ( + locator + ) + </li> +<li>verifyElementNotPresent + ( + locator + ) + </li> +<li>waitForElementPresent + ( + locator + ) + </li> +<li>waitForElementNotPresent + ( + locator + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeOrdered"></a>storeOrdered + + ( + locator1, +locator2, + + variableName + ) + + </strong> +</dt> +<dd>Check if these two elements have same parent and are ordered. Two same elements will +not be considered ordered.<p>Arguments:</p> +<ul> +<li>locator1 - an <a href="#locators">element locator</a> pointing to the first element</li> +<li>locator2 - an <a href="#locators">element locator</a> pointing to the second element</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if two elements are ordered and have same parent, false otherwise</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertOrdered + ( + locator1, locator2 + ) + </li> +<li>assertNotOrdered + ( + locator1, locator2 + ) + </li> +<li>verifyOrdered + ( + locator1, locator2 + ) + </li> +<li>verifyNotOrdered + ( + locator1, locator2 + ) + </li> +<li>waitForOrdered + ( + locator1, locator2 + ) + </li> +<li>waitForNotOrdered + ( + locator1, locator2 + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storePromptPresent"></a>storePromptPresent + + ( + + variableName + ) + + </strong> +</dt> +<dd>Has a prompt occurred? + +<p> +This function never throws an exception +</p> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if there is a pending prompt</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertPromptPresent + ( + + ) + </li> +<li>assertPromptNotPresent + ( + + ) + </li> +<li>verifyPromptPresent + ( + + ) + </li> +<li>verifyPromptNotPresent + ( + + ) + </li> +<li>waitForPromptPresent + ( + + ) + </li> +<li>waitForPromptNotPresent + ( + + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeSomethingSelected"></a>storeSomethingSelected + + ( + selectLocator, + + variableName + ) + + </strong> +</dt> +<dd>Determines whether some option in a drop-down menu is selected.<p>Arguments:</p> +<ul> +<li>selectLocator - an <a href="#locators">element locator</a> identifying a drop-down menu</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if some option has been selected, false otherwise</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertSomethingSelected + ( + selectLocator + ) + </li> +<li>assertNotSomethingSelected + ( + selectLocator + ) + </li> +<li>verifySomethingSelected + ( + selectLocator + ) + </li> +<li>verifyNotSomethingSelected + ( + selectLocator + ) + </li> +<li>waitForSomethingSelected + ( + selectLocator + ) + </li> +<li>waitForNotSomethingSelected + ( + selectLocator + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeTextPresent"></a>storeTextPresent + + ( + pattern, + + variableName + ) + + </strong> +</dt> +<dd>Verifies that the specified text pattern appears somewhere on the rendered page shown to the user.<p>Arguments:</p> +<ul> +<li>pattern - a <a href="#patterns">pattern</a> to match with the text of the page</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if the pattern matches the text, false otherwise</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertTextPresent + ( + pattern + ) + </li> +<li>assertTextNotPresent + ( + pattern + ) + </li> +<li>verifyTextPresent + ( + pattern + ) + </li> +<li>verifyTextNotPresent + ( + pattern + ) + </li> +<li>waitForTextPresent + ( + pattern + ) + </li> +<li>waitForTextNotPresent + ( + pattern + ) + </li> +</ul> +</dd> +<br> +<dt> +<strong><a name="storeVisible"></a>storeVisible + + ( + locator, + + variableName + ) + + </strong> +</dt> +<dd>Determines if the specified element is visible. An +element can be rendered invisible by setting the CSS "visibility" +property to "hidden", or the "display" property to "none", either for the +element itself or one if its ancestors. This method will fail if +the element is not present.<p>Arguments:</p> +<ul> +<li>locator - an <a href="#locators">element locator</a> +</li> +<li>variableName - + the name of a <a href="#storedVars">variable</a> in which the result is to be stored. + </li> +</ul> +<p> +<dl> +<dt>Returns: </dt> +<dd>true if the specified element is visible, false otherwise</dd> +</dl> +</p> +<p>Related Assertions, automatically generated:</p> +<ul> +<li>assertVisible + ( + locator + ) + </li> +<li>assertNotVisible + ( + locator + ) + </li> +<li>verifyVisible + ( + locator + ) + </li> +<li>verifyNotVisible + ( + locator + ) + </li> +<li>waitForVisible + ( + locator + ) + </li> +<li>waitForNotVisible + ( + locator + ) + </li> +</ul> +</dd> +<br> +</dl> +<h2> +<a name="parameter-construction-and-variables">Parameter construction and Variables</a> +</h2> +<blockquote> +<p>All Selenium command parameters can be constructed using both simple + variable substitution as well as full javascript. Both of these + mechanisms can access previously stored variables, but do so using + different syntax.</p> +<p> +<a name="storedVars"></a><strong>Stored Variables</strong> +</p> +<p>The commands <em>store</em>, <em>storeValue</em> and <em>storeText</em> can be used to store a variable + value for later access. Internally, these variables are stored in a map called "storedVars", + with values keyed by the variable name. These commands are documented in the command reference.</p> +<p> +<strong>Variable substitution</strong> +</p> +<p>Variable substitution provides a simple way to include a previously stored variable in a + command parameter. This is a simple mechanism, by which the variable to substitute is indicated + by ${variableName}. Multiple variables can be substituted, and intermixed with static text.</p> +<p>Example:</p> +<blockquote> +<table border="1" class="table"> +<colgroup> +<col width="18%"> +<col width="36%"> +<col width="45%"> +</colgroup> +<tbody valign="top"> +<tr> +<td>store</td><td>Mr</td><td>title</td> +</tr> +<tr> +<td>storeValue</td><td>nameField</td><td>surname</td> +</tr> +<tr> +<td>store</td><td>${title} ${surname}</td><td>fullname</td> +</tr> +<tr> +<td>type</td><td>textElement</td><td>Full name is: ${fullname}</td> +</tr> +</tbody> +</table> +</blockquote> +<p> +<strong>Javascript evaluation</strong> +</p> +<p>Javascript evaluation provides the full power of javascript in constructing a command parameter. + To use this mechanism, the <em>entire</em> parameter value must be prefixed by + 'javascript{' with a trailing '}'. The text inside the braces is evaluated as a javascript expression, + and can access previously stored variables using the <em>storedVars</em> map detailed above. + Note that variable substitution cannot be combined with javascript evaluation.</p> +<p>Example:</p> +<blockquote> +<table border="1" class="table"> +<colgroup> +<col width="9%"> +<col width="44%"> +<col width="46%"> +</colgroup> +<tbody valign="top"> +<tr> +<td>store</td><td>javascript{'merchant' + (new Date()).getTime()}</td><td>merchantId</td> +</tr> +<tr> +<td>type</td><td>textElement</td><td>javascript{storedVars['merchantId'].toUpperCase()}</td> +</tr> +</tbody> +</table> +</blockquote> +</blockquote> +<div class="section" id="extending-selenium"> +<h2> +<a name="extending-selenium">Extending Selenium</a> +</h2> +<blockquote> +<p>It can be quite simple to extend Selenium, adding your own actions, assertions and locator-strategies. + This is done with javascript by adding methods to the Selenium object prototype, and the PageBot + object prototype. On startup, Selenium will automatically look through methods on these prototypes, + using name patterns to recognise which ones are actions, assertions and locators.</p> +<p>The following examples try to give an indication of how Selenium can be extended with javascript.</p> +</blockquote> +<p> +<strong>Actions</strong> +</p> +<blockquote> +<p>All <em>doFoo</em> methods on the Selenium prototype are added as actions. For each action <em>foo</em> there + is also an action <em>fooAndWait</em> registered. An action method can take up to 2 parameters, which + will be passed the second and third column values in the test.</p> +<p>Example: Add a "typeRepeated" action to Selenium, which types the text twice into a text box.</p> +<pre class="literal-block"> + Selenium.prototype.doTypeRepeated = function(locator, text) { + // All locator-strategies are automatically handled by "findElement" + var element = this.page().findElement(locator); + + // Create the text to type + var valueToType = text + text; + + // Replace the element text with the new text + this.page().replaceText(element, valueToType); + }; + </pre> +</blockquote> +<p> +<strong>Accessors/Assertions</strong> +</p> +<blockquote> +<p>All <em>getFoo</em> and <em>isFoo</em> methods on the Selenium prototype are added as accessors (storeFoo). For each accessor there + is an <em>assertFoo</em>, <em>verifyFoo</em> and <em>waitForFoo</em> registered. An assert method can take up to 2 parameters, which + will be passed the second and third column values in the test. You can also define your own assertions literally + as simple "assert" methods, which will also auto-generate "verify" and "waitFor" commands.</p> +<p>Example: Add a <em>valueRepeated</em> assertion, that makes sure that the element value + consists of the supplied text repeated. The 2 commands that would be available in tests would be + <em>assertValueRepeated</em> and <em>verifyValueRepeated</em>.</p> +<pre class="literal-block"> + Selenium.prototype.assertValueRepeated = function(locator, text) { + // All locator-strategies are automatically handled by "findElement" + var element = this.page().findElement(locator); + + // Create the text to verify + var expectedValue = text + text; + + // Get the actual element value + var actualValue = element.value; + + // Make sure the actual value matches the expected + Assert.matches(expectedValue, actualValue); + }; + </pre> +</blockquote> +<p> +<strong>Automatic availability of storeFoo, assertFoo, assertNotFoo, waitForFoo and waitForNotFoo for every getFoo</strong> +</p> +<blockquote> +<p>All <em>getFoo</em> and <em>isFoo</em> methods on the Selenium prototype automatically result in the availability + of storeFoo, assertFoo, assertNotFoo, verifyFoo, verifyNotFoo, waitForFoo, and waitForNotFoo commands.</p> +<p>Example, if you add a getTextLength() method, the following commands will automatically be available: + storeTextLength, assertTextLength, assertNotTextLength, verifyTextLength, verifyNotTextLength, waitForTextLength, and waitForNotTextLength commands.</p> +<pre class="literal-block"> + Selenium.prototype.getTextLength = function(locator, text) { + return this.getText(locator).length; + }; + </pre> +<p>Also note that the <em>assertValueRepeated</em> method described above could have been implemented using + isValueRepeated, with the added benefit of also automatically getting assertNotValueRepeated, storeValueRepeated, + waitForValueRepeated and waitForNotValueRepeated.</p> +</blockquote> +<p> +<strong>Locator Strategies</strong> +</p> +<blockquote> +<p>All <em>locateElementByFoo</em> methods on the PageBot prototype are added as locator-strategies. A locator strategy takes 2 parameters, the first being the locator string (minus the prefix), and the second being the document in which to search.</p> +<p>Example: Add a "valuerepeated=" locator, that finds the first element a value attribute equal to the the supplied value repeated.</p> +<pre class="literal-block"> + // The "inDocument" is a the document you are searching. + PageBot.prototype.locateElementByValueRepeated = function(text, inDocument) { + // Create the text to search for + var expectedValue = text + text; + + // Loop through all elements, looking for ones that have + // a value === our expected value + var allElements = inDocument.getElementsByTagName("*"); + for (var i = 0; i < allElements.length; i++) { + var testElement = allElements[i]; + if (testElement.value && testElement.value === expectedValue) { + return testElement; + } + } + return null; + }; + </pre> +</blockquote> +<p> +<strong>user-extensions.js</strong> +</p> +<blockquote> +<p>By default, Selenium looks for a file called "user-extensions.js", and loads the javascript code found in that file. This file provides a convenient location for adding features to Selenium, without needing to modify the core Selenium sources.</p> +<p>In the standard distibution, this file does not exist. Users can create this file and place their extension code in this common location, removing the need to modify the Selenium sources, and hopefully assisting with the upgrade process.</p> +</blockquote> +</div> +</body> +</html> |