selenium

Selenium is a chemical element with symbol Se and atomic number 34. It is a nonmetal with properties that are intermediate between those of its periodic table column-adjacent chalcogen elements sulfur and tellurium. [read more at http://en.wikipedia.org/wiki/Selenium]

  • open.qa.logo
    Selenium is a test tool for web applications. Selenium tests run directly in a browser, just like real users do. It runs in Internet Explorer, Mozilla and Firefox on Windows, Linux, and Macintosh, Safari on the Mac.  They have plans to target Safari on the iPhone in some months. The tool is free and available under Apache 2.0.
    Since I have clearly quality issues during the development/releasing of my components for Joomla!, I am trying now to use the same tooling I daily use in java EE solutions for PHP...In this series I will present you some ideas (Unit testing, Continuous integration, code quality) that you may want to put in use as well.

    The quickest way to learn Selenium is via a Firefox plugin called Selenium IDE. It is quite compelling
    for developing tests in and quickly trying out Selenium before choosing Selenium for your project.

    There are two modes of operation for Selenium - Coreand Remote Control (RC).  Remote Control
    mode also has a related capability called Selenium Grid that allows you to throw hardware at tests
    to make it all faster.

    This tools is able to:

    • Simulate any action a human user may do either with the help of the keyboard or the mouse,
      this go from entering a text to select values in select list.
    • These workflow can be save and replay at any time and any speed.
    • You may group a set of tests and form a test suite very easily.
    • Export tests to Ruby, Python, Perl, Java .Net to run them in a non graphical environment ().

     

    Selenium is made of 3 components:

    • Selenium Core : the core must be installed on your server where the web applications are running.
    • Selenium IDE : is a Firefox/IE/Mozilla extension Firefox able to record, execute tests and test suites
    • Selenium Remote Control is a server which let you execute tests targeting many different browser,
      Firefox, Internet Explorer, opera and different operating system GNU/Linux,Mac OS and  MS Windows
      in also many different languages Ruby, Python, Perl, Java .Net.

    Also don't use Selenium for load testing web applications!, use Apache JMETER  instead. Attention Selenium
    has some issues when he has to work on 2 windows at the same time (pop -up).

    Today let just try Selenium IDE

    To make it work with Joomla!, or with any other web applications, just install the Firefox plugins, and start
    it by going to the tools menu of Firefox.

    Lets say that we want to test the contact page of my site for proper operations...In Firefox, go to the menu Tools

    selenium1

    This will open a floating windows, which let you define a script step by step in the windows ff0000">Script

    You may come with a test case similar to the one presented here:

    selenium-joomla-test

    The number of commands is huge, but well documented in the tab reference (ff0000">B)

    The base URL is my site (http://www.waltercedric.com), the test case, open the contact page, check the
    title of the page, enter some values in form, check for button and texts and submit the form.

    The menu selenium2  let you run the test by clicking on selenium3 you can see the
    result, if everything is green then the test has succeed.

    selenium4

    and you see every step of the test case in the browser windows:

    selenium6 

    As you see it is quite easy to develop a script to test a page, test can be saved on disk  in different format,
    so you can execute them in Selenium Core

    selenium5

    So the test developed for testing the contact page of Joomla! now look like:

       1: package com.example.tests;
       2:  
       3: import com.thoughtworks.selenium.*;
       4: import java.util.regex.Pattern;
       5:  
       6: public class NewTest extends SeleneseTestCase {
       7:     public void setUp() throws Exception {
       8:         setUp("http://www.waltercedric.com/", "*chrome");
       9:     }
      10:     public void testNew() throws Exception {
      11:         // selenium.("http://www.waltercedric.com/-contact-me.html");
      12:         assertEquals("Contact - Cedric Walter", selenium.getTitle());
      13:         selenium.type("contact_name", "cedric");
     14:  selenium.type("contact_email", "This email address is being protected from spambots. You need JavaScript enabled to view it.");
      15:         selenium.type("contact_subject", "Selenium is great, try it");
      16:         verifyTrue(selenium.isTextPresent("Enter your Message:"));
      17:         selenium.type("contact_text", "Hi Cedric. selenium would be cool for testing securityimages!");
      18:         verifyTrue(selenium.isTextPresent("Send"));
      19:         selenium.submit("emailForm");
      20:         selenium.waitForPageToLoad("30000");
      21:     }
      22: }
    .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: 008000; } .csharpcode .kwrd { color: 0000ff; } .csharpcode .str { color: 006080; } .csharpcode .op { color: 0000c0; } .csharpcode .preproc { color: cc6633; } .csharpcode .asp { background-color: ffff00; } .csharpcode .html { color: 800000; } .csharpcode .attr { color: ff0000; } .csharpcode .alt { background-color: f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: 606060; }

    Or better in PHP so you can reuse it in XINC continuous integration server (more to come on XINC in a future article)

       1: <?php
       2:  
       3: require_once 'PHPUnit/Extensions/SeleniumTestCase.php';
       4:  
       5: class Example extends PHPUnit_Extensions_SeleniumTestCase
       6: {
       7:   function setUp()
       8:   {
       9:     $this->setBrowser("*chrome");
      10:     $this->setBrowserUrl("http://www.waltercedric.com/");
      11:   }
      12:  
      13:   function testMyTestCase()
      14:   {
      15:     // $this->("http://www.waltercedric.com/-contact-me.html");
      16:     $this->assertEquals("Contact - Cedric Walter", $this->getTitle());
      17:     $this->type("contact_name", "cedric");
     18:  $this->type("contact_email", "This email address is being protected from spambots. You need JavaScript enabled to view it.");
      19:     $this->type("contact_subject", "Selenium is great, try it");
      20:     try {
      21:         $this->assertTrue($this->isTextPresent("Enter your Message:"));
      22:     } catch (PHPUnit_Framework_AssertionFailedError $e) {
      23:         array_push($this->verificationErrors, $e->toString());
      24:     }
      25:     $this->type("contact_text", "Hi Cedric. selenium would be cool for testing securityimages!");
      26:     try {
      27:         $this->assertTrue($this->isTextPresent("Send"));
      28:     } catch (PHPUnit_Framework_AssertionFailedError $e) {
      29:         array_push($this->verificationErrors, $e->toString());
      30:     }
      31:     $this->submit("emailForm");
      32:     $this->waitForPageToLoad("30000");
      33:   }
      34: }
      35: ?>
    .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: 008000; } .csharpcode .kwrd { color: 0000ff; } .csharpcode .str { color: 006080; } .csharpcode .op { color: 0000c0; } .csharpcode .preproc { color: cc6633; } .csharpcode .asp { background-color: ffff00; } .csharpcode .html { color: 800000; } .csharpcode .attr { color: ff0000; } .csharpcode .alt { background-color: f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: 606060; }

    As soon as You have a set of tests, this can form a Test Suite.

    SecurityImages for Joomla create Captcha, so it is quite difficult for a tool to pass the Turin test
    (aka recognize the scrambled images), this point apart, I am now developing testcases to test the
    admin backend, frontend Joomla! patches. These test will be available in the component itself, so
    anybody can run them with little efforts.

    Read more at:

     


    ff0000">Here is the list of all commands, use search in page to quickly find the right command.

    addLocationStrategy ( strategyName,functionDefinition )
    Defines a new function for Selenium to locate elements on the page. For example, if you
    define the strategy "foo", and someone runs click("foo=blah"), we'll run your function, passing
    you the string "blah", and click on the element that your function returns, or throw an "Element
    not found" error if your function returns null. We'll pass three arguments to your function:
    • locator: the string the user passed in
    • inWindow: the currently selected window
    • inDocument: the currently selected document
    The function must return null if the element can't be found.

    Arguments:

    • strategyName - the name of the strategy to define; this should use only letters [a-zA-Z] with
    • no spaces or other punctuation.
    • functionDefinition - a string defining the body of a function in JavaScript. For example: return inDocument.getElementById(locator);

    addSelection ( locator,optionLocator )
    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

    Arguments:

    • locator - an element locator identifying a multi-select box
    • optionLocator - an option locator (a label by default)

    allowNativeXpath ( allow )
    Specifies whether Selenium should use the native in-browser implementation of XPath (if any native
    version is available); if you pass "false" to this function, we will always use our pure-JavaScript xpath
    library. Using the pure-JS xpath library can improve the consistency of xpath element locators
    between different browser vendors, but the pure-JS version is much slower than the native implementations.

    Arguments:

    • allow - boolean, true means we'll prefer to use native XPath; false means we'll only use JS XPath

    altKeyDown ( )
    Press the alt key and hold it down until doAltUp() is called or a new page is loaded.
    altKeyUp ( )
    Release the alt key.
    answerOnNextPrompt ( answer )
    Instructs Selenium to return the specified answer string in response to the next JavaScript
    prompt [window.prompt()].

    Arguments:

    • answer - the answer to give in response to the prompt pop-up

    assignId ( locator,identifier )
    Temporarily sets the "id" attribute of the specified element, so you can locate it in the
    future using its ID rather than a slow/complicated XPath. This ID will disappear once the page is reloaded.

    Arguments:

    • locator - an element locator pointing to an element
    • identifier - a string to be used as the ID of the specified element

    break ( )
    Halt the currently running test, and wait for the user to press the Continue button. This command
    is useful for debugging, but be careful when using it, because it will force automated tests to hang
    until a user intervenes manually.
    captureEntirePageScreenshot ( filename )
    Saves the entire contents of the current window canvas to a PNG file. Currently this only works in
    Mozilla and when running in chrome mode. Contrast this with the captureScreenshot command,
    which captures the contents of the OS viewport (i.e. whatever is currently being displayed on
    the monitor), and is implemented in the RC only. Implementation mostly borrowed from the
    Screengrab! Firefox extension. Please see http://www.screengrab.org for details.

    Arguments:

    • filename - the path to the file to persist the screenshot as. No filename extension will be appended by default. Directories will not be created if they do not exist, and an exception will be thrown, possibly by native code.

    check ( locator )
    Check a toggle-button (checkbox/radio)

    Arguments:


    chooseCancelOnNextConfirmation ( )
    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. Selenium will then resume using the default behavior for future confirmations, automatically returning true (OK) unless/until you explicitly call this command for each confirmation.
    chooseOkOnNextConfirmation ( )
    Undo the effect of calling chooseCancelOnNextConfirmation. Note that Selenium's overridden window.confirm() function will normally automatically return true, as if the user had manually clicked OK, so you shouldn't need to use this command unless for some reason you need to change your mind prior to the next confirmation. After any confirmation, Selenium will resume using the default behavior for future confirmations, automatically returning true (OK) unless/until you explicitly call chooseCancelOnNextConfirmation for each confirmation.
    click ( locator )
    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.

    Arguments:

    • locator - an element locator

    clickAt ( locator,coordString )
    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.

    Arguments:

    • locator - an element locator
    • coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.

    close ( )
    Simulates the user clicking the "close" button in the titlebar of a popup window or tab.
    contextMenu ( locator )
    Simulates opening the context menu for the specified element (as might happen if the user "right-clicked" on the element).

    Arguments:

    • locator - an element locator

    contextMenuAt ( locator,coordString )
    Simulates opening the context menu for the specified element (as might happen if the user "right-clicked" on the element).

    Arguments:

    • locator - an element locator
    • coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.

    controlKeyDown ( )
    Press the control key and hold it down until doControlUp() is called or a new page is loaded.
    controlKeyUp ( )
    Release the control key.
    createCookie ( nameValuePair,optionsString )
    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.

    Arguments:

    • nameValuePair - name and value of the cookie in a format "name=value"
    • optionsString - options for the cookie. Currently supported options include 'path', 'max_age' and 'domain'. the optionsString's format is "path=/path/, max_age=60, domain=.foo.com". The order of options are irrelevant, the unit of the value of 'max_age' is second. Note that specifying a domain that isn't a subset of the current domain will usually fail.

    deleteAllVisibleCookies ( )
    Calls deleteCookie with recurse=true on all cookies visible to the current page. As noted on the documentation for deleteCookie, recurse=true can be much slower than simply deleting the cookies using a known domain/path.
    deleteCookie ( name,optionsString )
    Delete a named cookie with specified path and domain. Be careful; to delete a cookie, you need to delete it using the exact same path and domain that were used to create the cookie. If the path is wrong, or the domain is wrong, the cookie simply won't be deleted. Also note that specifying a domain that isn't a subset of the current domain will usually fail. Since there's no way to discover at runtime the original path and domain of a given cookie, we've added an option called 'recurse' to try all sub-domains of the current domain with all paths that are a subset of the current path. Beware; this option can be slow. In big-O notation, it operates in O(n*m) time, where n is the number of dots in the domain name and m is the number of slashes in the path.

    Arguments:

    • name - the name of the cookie to be deleted
    • optionsString - options for the cookie. Currently supported options include 'path', 'domain' and 'recurse.' The optionsString's format is "path=/path/, domain=.foo.com, recurse=true". The order of options are irrelevant. Note that specifying a domain that isn't a subset of the current domain will usually fail.

    doubleClick ( locator )
    Double clicks on a link, button, checkbox or radio button. If the double click action causes a new page to load (like a link usually does), call waitForPageToLoad.

    Arguments:

    • locator - an element locator

    doubleClickAt ( locator,coordString )
    Doubleclicks on a link, button, checkbox or radio button. If the action causes a new page to load (like a link usually does), call waitForPageToLoad.

    Arguments:

    • locator - an element locator
    • coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.

    dragAndDrop ( locator,movementsString )
    Drags an element a certain distance and then drops it

    Arguments:

    • locator - an element locator
    • movementsString - offset in pixels from the current location to which the element should be moved, e.g., "+70,-300"

    dragAndDropToObject ( locatorOfObjectToBeDragged,locatorOfDragDestinationObject )
    Drags an element and drops it on another element

    Arguments:

    • locatorOfObjectToBeDragged - an element to be dragged
    • locatorOfDragDestinationObject - an element whose location (i.e., whose center-most pixel) will be the point where locatorOfObjectToBeDragged is dropped

    dragdrop ( locator,movementsString )
    deprecated - use dragAndDrop instead

    Arguments:

    • locator - an element locator
    • movementsString - offset in pixels from the current location to which the element should be moved, e.g., "+70,-300"

    echo ( message )
    Prints the specified message into the third table cell in your Selenese tables. Useful for debugging.

    Arguments:

    • message - the message to print

    fireEvent ( locator,eventName )
    Explicitly simulate an event, to trigger the corresponding "onevent" handler.

    Arguments:

    • locator - an element locator
    • eventName - the event name, e.g. "focus" or "blur"

    focus ( locator )
    Move the focus to the specified element; for example, if the element is an input field, move the cursor to that field.

    Arguments:


    goBack ( )
    Simulates the user clicking the "back" button on their browser.
    highlight ( locator )
    Briefly changes the backgroundColor of the specified element yellow. Useful for debugging.

    Arguments:


    ignoreAttributesWithoutValue ( ignore )
    Specifies whether Selenium will ignore xpath attributes that have no value, i.e. are the empty string, when using the non-native xpath evaluation engine. You'd want to do this for performance reasons in IE. However, this could break certain xpaths, for example an xpath that looks for an attribute whose value is NOT the empty string. The hope is that such xpaths are relatively rare, but the user should have the option of using them. Note that this only influences xpath evaluation when using the ajaxslt engine (i.e. not "javascript-xpath").

    Arguments:

    • ignore - boolean, true means we'll ignore attributes without value at the expense of xpath "correctness"; false means we'll sacrifice speed for correctness.

    keyDown ( locator,keySequence )
    Simulates a user pressing a key (without releasing it yet).

    Arguments:

    • locator - an element locator
    • 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".

    keyPress ( locator,keySequence )
    Simulates a user pressing and releasing a key.

    Arguments:

    • locator - an element locator
    • 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".

    keyUp ( locator,keySequence )
    Simulates a user releasing a key.

    Arguments:

    • locator - an element locator
    • 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".

    metaKeyDown ( )
    Press the meta key and hold it down until doMetaUp() is called or a new page is loaded.
    metaKeyUp ( )
    Release the meta key.
    mouseDown ( locator )
    Simulates a user pressing the mouse button (without releasing it yet) on the specified element.

    Arguments:


    mouseDownAt ( locator,coordString )
    Simulates a user pressing the mouse button (without releasing it yet) at the specified location.

    Arguments:

    • locator - an element locator
    • coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.

    mouseMove ( locator )
    Simulates a user pressing the mouse button (without releasing it yet) on the specified element.

    Arguments:


    mouseMoveAt ( locator,coordString )
    Simulates a user pressing the mouse button (without releasing it yet) on the specified element.

    Arguments:

    • locator - an element locator
    • coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.

    mouseOut ( locator )
    Simulates a user moving the mouse pointer away from the specified element.

    Arguments:


    mouseOver ( locator )
    Simulates a user hovering a mouse over the specified element.

    Arguments:


    mouseUp ( locator )
    Simulates the event that occurs when the user releases the mouse button (i.e., stops holding the button down) on the specified element.

    Arguments:


    mouseUpAt ( locator,coordString )
    Simulates the event that occurs when the user releases the mouse button (i.e., stops holding the button down) at the specified location.

    Arguments:

    • locator - an element locator
    • coordString - specifies the x,y position (i.e. - 10,20) of the mouse event relative to the element returned by the locator.

    open ( url )
    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. Note: 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.

    Arguments:

    • url - the URL to open; may be relative or absolute

    openWindow ( url,windowID )
    Opens a popup window (if a window with that ID isn't already open). After opening the window, you'll need to select it using the selectWindow command.

    This command can also be a useful workaround for bug SEL-339. In some cases, Selenium will be unable to intercept a call to window.open (if the call occurs during or before the "onLoad" event, for example). In those cases, you can force Selenium to notice the open window's name by using the Selenium openWindow command, using an empty (blank) url, like this: openWindow("", "myFunnyWindow").

    Arguments:

    • url - the URL to open, which can be blank
    • windowID - the JavaScript window ID of the window to select

    pause ( waitTime )
    Wait for the specified amount of time (in milliseconds)

    Arguments:

    • waitTime - the amount of time to sleep (in milliseconds)

    refresh ( )
    Simulates the user clicking the "Refresh" button on their browser.
    removeAllSelections ( locator )
    Unselects all of the selected options in a multi-select element.

    Arguments:


    removeSelection ( locator,optionLocator )
    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

    Arguments:

    • locator - an element locator identifying a multi-select box
    • optionLocator - an option locator (a label by default)

    runScript ( script )
    Creates a new "script" tag in the body of the current test window, and adds the specified text into the body of the command. Scripts run in this way can often be debugged more easily than scripts executed using Selenium's "getEval" command. Beware that JS exceptions thrown in these script tags aren't managed by Selenium, so you should probably wrap your script in try/catch blocks if there is any chance that the script will throw an exception.

    Arguments:

    • script - the JavaScript snippet to run

    select ( selectLocator,optionLocator )
    Select an option from a drop-down using an option locator.

    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.

    • label=labelPattern: matches options based on their labels, i.e. the visible text. (This is the default.)
      • label=regexp:^[Oo]ther
    • value=valuePattern: matches options based on their values.
      • value=other
    • id=id: matches options based on their ids.
      • id=option1
    • index=index: matches an option based on its index (offset from zero).
      • index=2

    If no option locator prefix is provided, the default behaviour is to match on label.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • optionLocator - an option locator (a label by default)

    selectFrame ( locator )
    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". You can also select a frame by its 0-based index number; select the first frame with "index=0", or the third frame with "index=2".

    You may also use a DOM expression to identify the frame you want directly, like this: dom=frames["main"].frames["subframe"]

    Arguments:


    selectWindow ( windowID )
    Selects a popup window using a window locator; once a popup window has been selected, all commands go to that window. To select the main window again, use null as the target.

    Window locators provide different ways of specifying the window object: by title, by internal JavaScript "name," or by JavaScript variable.

    • title=My Special Window: Finds the window using the text that appears in the title bar. Be careful; two windows can share the same title. If that happens, this locator will just pick one.
    • name=myWindow: Finds the window using its internal JavaScript "name" property. This is the second parameter "windowName" passed to the JavaScript method window.open(url, windowName, windowFeatures, replaceFlag) (which Selenium intercepts).
    • var=variableName: Some pop-up windows are unnamed (anonymous), but are associated with a JavaScript variable name in the current application window, e.g. "window.foo = window.open(url);". In those cases, you can open the window using "var=foo".

    If no window locator prefix is provided, we'll try to guess what you mean like this:

    1.) if windowID is null, (or the string "null") then it is assumed the user is referring to the original window instantiated by the browser).

    2.) if the value of the "windowID" parameter is a JavaScript variable name in the current application window, then it is assumed that this variable contains the return value from a call to the JavaScript window.open() method.

    3.) Otherwise, selenium looks in a hash it maintains that maps string names to window "names".

    4.) If that fails, we'll try looping over all of the known windows to try to find the appropriate "title". Since "title" is not necessarily unique, this may have unexpected behavior.

    If you're having trouble figuring out the name of a window that you want to manipulate, look at the Selenium log messages which identify the names of windows created via window.open (and therefore intercepted by Selenium). You will see messages like the following for each window as it is opened:

    debug: window.open call intercepted; window ID (which you can use with selectWindow()) is "myNewWindow"

    In some cases, Selenium will be unable to intercept a call to window.open (if the call occurs during or before the "onLoad" event, for example). (This is bug SEL-339.) In those cases, you can force Selenium to notice the open window's name by using the Selenium openWindow command, using an empty (blank) url, like this: openWindow("", "myFunnyWindow").

    Arguments:

    • windowID - the JavaScript window ID of the window to select

    setBrowserLogLevel ( logLevel )
    Sets the threshold for browser-side logging messages; log messages beneath this threshold will be discarded. Valid logLevel strings are: "debug", "info", "warn", "error" or "off". To see the browser logs, you need to either show the log window in GUI mode, or enable browser-side logging in Selenium RC.

    Arguments:

    • logLevel - one of the following: "debug", "info", "warn", "error" or "off"

    setCursorPosition ( locator,position )
    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.

    Arguments:

    • locator - an element locator pointing to an input element or textarea
    • 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.

    setMouseSpeed ( pixels )
    Configure the number of pixels between "mousemove" events during dragAndDrop commands (default=10).

    Setting this value to 0 means that we'll send a "mousemove" event to every single pixel in between the start location and the end location; that can be very slow, and may cause some browsers to force the JavaScript to timeout.

    If the mouse speed is greater than the distance between the two dragged objects, we'll just send one "mousemove" at the start location and then one final one at the end location.

    Arguments:

    • pixels - the number of pixels between "mousemove" events

    setSpeed ( value )
    Set execution speed (i.e., set the millisecond length of a delay which will follow each selenium operation). By default, there is no such delay, i.e., the delay is 0 milliseconds.

    Arguments:

    • value - the number of milliseconds to pause after operation

    setTimeout ( timeout )
    Specifies the amount of time that Selenium will wait for actions to complete.

    Actions that require waiting include "open" and the "waitFor*" actions.

    The default timeout is 30 seconds.

    Arguments:

    • timeout - a timeout in milliseconds, after which the action will return with an error

    shiftKeyDown ( )
    Press the shift key and hold it down until doShiftUp() is called or a new page is loaded.
    shiftKeyUp ( )
    Release the shift key.
    store ( expression,variableName )
    This command is a synonym for storeExpression.

    Arguments:

    • expression - the value to store
    • variableName - the name of a variable in which the result is to be stored.

    submit ( formLocator )
    Submit the specified form. This is particularly useful for forms without submit buttons, e.g. single-input "Search" forms.

    Arguments:


    type ( locator,value )
    Sets the value of an input field, as though you typed it in.

    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.

    Arguments:


    typeKeys ( locator,value )
    Simulates keystroke events on the specified element, as though you typed the value key-by-key.

    This is a convenience method for calling keyDown, keyUp, keyPress for every character in the specified string; this is useful for dynamic UI widgets (like auto-completing combo boxes) that require explicit key events.

    Unlike the simple "type" command, which forces the specified value into the page directly, this command may or may not have any visible effect, even in cases where typing keys would normally have a visible effect. For example, if you use "typeKeys" on a form element, you may or may not see the results of what you typed in the field.

    In some cases, you may need to use the simple "type" command to set the value of the field and then the "typeKeys" command to send the keystroke events corresponding to what you just typed.

    Arguments:


    uncheck ( locator )
    Uncheck a toggle-button (checkbox/radio)

    Arguments:


    waitForCondition ( script,timeout )
    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.

    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 selenium.browserbot.getCurrentWindow(), and then run your JavaScript in there

    Arguments:

    • script - the JavaScript snippet to run
    • timeout - a timeout in milliseconds, after which this command will return with an error

    waitForFrameToLoad ( frameAddress,timeout )
    Waits for a new frame to load.

    Selenium constantly keeps track of new pages and frames loading, and sets a "newPageLoaded" flag when it first notices a page load.

    See waitForPageToLoad for more information.

    Arguments:

    • frameAddress - FrameAddress from the server side
    • timeout - a timeout in milliseconds, after which this command will return with an error

    waitForPageToLoad ( timeout )
    Waits for a new page to load.

    You can use this command instead of the "AndWait" suffixes, "clickAndWait", "selectAndWait", "typeAndWait" etc. (which are only available in the JS API).

    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.

    Arguments:

    • timeout - a timeout in milliseconds, after which this command will return with an error

    waitForPopUp ( windowID,timeout )
    Waits for a popup window to appear and load up.

    Arguments:

    • windowID - the JavaScript window "name" of the window that will appear (not the text of the title bar)
    • timeout - a timeout in milliseconds, after which the action will return with an error

    windowFocus ( )
    Gives focus to the currently selected window
    windowMaximize ( )
    Resize currently selected window to take up the entire screen

    Selenium Accessors

    assertErrorOnNext ( message )
    Tell Selenium to expect an error on the next command execution.

    Arguments:

    • message - The error message we should expect. This command will fail if the wrong error message appears.

    Related Assertions, automatically generated:

    • assertNotErrorOnNext ( message )
    • verifyErrorOnNext ( message )
    • verifyNotErrorOnNext ( message )
    • waitForErrorOnNext ( message )
    • waitForNotErrorOnNext ( message )

    assertFailureOnNext ( message )
    Tell Selenium to expect a failure on the next command execution.

    Arguments:

    • message - The failure message we should expect. This command will fail if the wrong failure message appears.

    Related Assertions, automatically generated:

    • assertNotFailureOnNext ( message )
    • verifyFailureOnNext ( message )
    • verifyNotFailureOnNext ( message )
    • waitForFailureOnNext ( message )
    • waitForNotFailureOnNext ( message )

    assertSelected ( selectLocator,optionLocator )
    Verifies that the selected option of a drop-down satisfies the optionSpecifier. Note that this command is deprecated; you should use assertSelectedLabel, assertSelectedValue, assertSelectedIndex, or assertSelectedId instead.

    See the select command for more information about option locators.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • optionLocator - an option locator, typically just an option label (e.g. "John Smith")

    Related Assertions, automatically generated:

    • assertNotSelected ( selectLocator, optionLocator )
    • verifySelected ( selectLocator, optionLocator )
    • verifyNotSelected ( selectLocator, optionLocator )
    • waitForSelected ( selectLocator, optionLocator )
    • waitForNotSelected ( selectLocator, optionLocator )

    storeAlert ( variableName )
    Retrieves the message of a JavaScript alert generated during the previous action, or fail if there were no alerts.

    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.

    NOTE: under Selenium, JavaScript alerts will NOT pop up a visible alert dialog.

    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.

    Returns:
    The message of the most recent JavaScript alert

    Related Assertions, automatically generated:


    storeAllButtons ( variableName )
    Returns the IDs of all buttons on the page.

    If a given button has no ID, it will appear as "" in this array.

    Returns:
    the IDs of all buttons on the page

    Related Assertions, automatically generated:


    storeAllFields ( variableName )
    Returns the IDs of all input fields on the page.

    If a given field has no ID, it will appear as "" in this array.

    Returns:
    the IDs of all field on the page

    Related Assertions, automatically generated:


    storeAllLinks ( variableName )
    Returns the IDs of all links on the page.

    If a given link has no ID, it will appear as "" in this array.

    Returns:
    the IDs of all links on the page

    Related Assertions, automatically generated:


    storeAllWindowIds ( variableName )
    Returns the IDs of all windows that the browser knows about.
    Returns:
    the IDs of all windows that the browser knows about.

    Related Assertions, automatically generated:


    storeAllWindowNames ( variableName )
    Returns the names of all windows that the browser knows about.
    Returns:
    the names of all windows that the browser knows about.

    Related Assertions, automatically generated:

    • assertAllWindowNames ( pattern )
    • assertNotAllWindowNames ( pattern )
    • verifyAllWindowNames ( pattern )
    • verifyNotAllWindowNames ( pattern )
    • waitForAllWindowNames ( pattern )
    • waitForNotAllWindowNames ( pattern )

    storeAllWindowTitles ( variableName )
    Returns the titles of all windows that the browser knows about.
    Returns:
    the titles of all windows that the browser knows about.

    Related Assertions, automatically generated:

    • assertAllWindowTitles ( pattern )
    • assertNotAllWindowTitles ( pattern )
    • verifyAllWindowTitles ( pattern )
    • verifyNotAllWindowTitles ( pattern )
    • waitForAllWindowTitles ( pattern )
    • waitForNotAllWindowTitles ( pattern )

    storeAttribute ( attributeLocator, variableName )
    Gets the value of an element attribute. The value of the attribute may differ across browsers (this is the case for the "style" attribute, for example).

    Arguments:

    • attributeLocator - an element locator followed by an @ sign and then the name of the attribute, e.g. "foo@bar"
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the value of the specified attribute

    Related Assertions, automatically generated:

    • assertAttribute ( attributeLocator, pattern )
    • assertNotAttribute ( attributeLocator, pattern )
    • verifyAttribute ( attributeLocator, pattern )
    • verifyNotAttribute ( attributeLocator, pattern )
    • waitForAttribute ( attributeLocator, pattern )
    • waitForNotAttribute ( attributeLocator, pattern )

    storeAttributeFromAllWindows ( attributeName, variableName )
    Returns every instance of some attribute from all known windows.

    Arguments:

    • attributeName - name of an attribute on the windows
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the set of values of this attribute from all known windows.

    Related Assertions, automatically generated:

    • assertAttributeFromAllWindows ( attributeName, pattern )
    • assertNotAttributeFromAllWindows ( attributeName, pattern )
    • verifyAttributeFromAllWindows ( attributeName, pattern )
    • verifyNotAttributeFromAllWindows ( attributeName, pattern )
    • waitForAttributeFromAllWindows ( attributeName, pattern )
    • waitForNotAttributeFromAllWindows ( attributeName, pattern )

    storeBodyText ( variableName )
    Gets the entire text of the page.
    Returns:
    the entire text of the page

    Related Assertions, automatically generated:


    storeConfirmation ( variableName )
    Retrieves the message of a JavaScript confirmation dialog generated during the previous action.

    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.

    NOTE: under Selenium, JavaScript confirmations will NOT pop up a visible dialog.

    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.

    Returns:
    the message of the most recent JavaScript confirmation dialog

    Related Assertions, automatically generated:


    storeCookie ( variableName )
    Return all cookies of the current page under test.
    Returns:
    all cookies of the current page under test

    Related Assertions, automatically generated:


    storeCookieByName ( name, variableName )
    Returns the value of the cookie with the specified name, or throws an error if the cookie is not present.

    Arguments:

    • name - the name of the cookie
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the value of the cookie

    Related Assertions, automatically generated:

    • assertCookieByName ( name, pattern )
    • assertNotCookieByName ( name, pattern )
    • verifyCookieByName ( name, pattern )
    • verifyNotCookieByName ( name, pattern )
    • waitForCookieByName ( name, pattern )
    • waitForNotCookieByName ( name, pattern )

    storeCursorPosition ( locator, variableName )
    Retrieves the text cursor position in the given input element or textarea; beware, this may not work perfectly on all browsers.

    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 SEL-243.

    This method will fail if the specified element isn't an input element or textarea, or there is no cursor in the element.

    Arguments:

    • locator - an element locator pointing to an input element or textarea
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the numerical position of the cursor in the field

    Related Assertions, automatically generated:

    • assertCursorPosition ( locator, pattern )
    • assertNotCursorPosition ( locator, pattern )
    • verifyCursorPosition ( locator, pattern )
    • verifyNotCursorPosition ( locator, pattern )
    • waitForCursorPosition ( locator, pattern )
    • waitForNotCursorPosition ( locator, pattern )

    storeElementHeight ( locator, variableName )
    Retrieves the height of an element

    Arguments:

    • locator - an element locator pointing to an element
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    height of an element in pixels

    Related Assertions, automatically generated:

    • assertElementHeight ( locator, pattern )
    • assertNotElementHeight ( locator, pattern )
    • verifyElementHeight ( locator, pattern )
    • verifyNotElementHeight ( locator, pattern )
    • waitForElementHeight ( locator, pattern )
    • waitForNotElementHeight ( locator, pattern )

    storeElementIndex ( locator, variableName )
    Get the relative index of an element to its parent (starting from 0). The comment node and empty text node will be ignored.

    Arguments:

    • locator - an element locator pointing to an element
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    of relative index of the element to its parent (starting from 0)

    Related Assertions, automatically generated:

    • assertElementIndex ( locator, pattern )
    • assertNotElementIndex ( locator, pattern )
    • verifyElementIndex ( locator, pattern )
    • verifyNotElementIndex ( locator, pattern )
    • waitForElementIndex ( locator, pattern )
    • waitForNotElementIndex ( locator, pattern )

    storeElementPositionLeft ( locator, variableName )
    Retrieves the horizontal position of an element

    Arguments:

    • locator - an element locator pointing to an element OR an element itself
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    of pixels from the edge of the frame.

    Related Assertions, automatically generated:

    • assertElementPositionLeft ( locator, pattern )
    • assertNotElementPositionLeft ( locator, pattern )
    • verifyElementPositionLeft ( locator, pattern )
    • verifyNotElementPositionLeft ( locator, pattern )
    • waitForElementPositionLeft ( locator, pattern )
    • waitForNotElementPositionLeft ( locator, pattern )

    storeElementPositionTop ( locator, variableName )
    Retrieves the vertical position of an element

    Arguments:

    • locator - an element locator pointing to an element OR an element itself
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    of pixels from the edge of the frame.

    Related Assertions, automatically generated:

    • assertElementPositionTop ( locator, pattern )
    • assertNotElementPositionTop ( locator, pattern )
    • verifyElementPositionTop ( locator, pattern )
    • verifyNotElementPositionTop ( locator, pattern )
    • waitForElementPositionTop ( locator, pattern )
    • waitForNotElementPositionTop ( locator, pattern )

    storeElementWidth ( locator, variableName )
    Retrieves the width of an element

    Arguments:

    • locator - an element locator pointing to an element
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    width of an element in pixels

    Related Assertions, automatically generated:

    • assertElementWidth ( locator, pattern )
    • assertNotElementWidth ( locator, pattern )
    • verifyElementWidth ( locator, pattern )
    • verifyNotElementWidth ( locator, pattern )
    • waitForElementWidth ( locator, pattern )
    • waitForNotElementWidth ( locator, pattern )

    storeEval ( script, variableName )
    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.

    Note that, by default, the snippet will run in the context of the "selenium" object itself, so this will refer to the Selenium object. Use window to refer to the window of your application, e.g. window.document.getElementById('foo')

    If you need to use a locator to refer to a single element in your application page, you can use this.browserbot.findElement("id=foo") where "id=foo" is your locator.

    Arguments:

    • script - the JavaScript snippet to run
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the results of evaluating the snippet

    Related Assertions, automatically generated:


    storeExpression ( expression, variableName )
    Returns the specified expression.

    This is useful because of JavaScript preprocessing. It is used to generate commands like assertExpression and waitForExpression.

    Arguments:

    • expression - the value to return
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the value passed in

    Related Assertions, automatically generated:

    • assertExpression ( expression, pattern )
    • assertNotExpression ( expression, pattern )
    • verifyExpression ( expression, pattern )
    • verifyNotExpression ( expression, pattern )
    • waitForExpression ( expression, pattern )
    • waitForNotExpression ( expression, pattern )

    storeHtmlSource ( variableName )
    Returns the entire HTML source between the opening and closing "html" tags.
    Returns:
    the entire HTML source

    Related Assertions, automatically generated:


    storeLocation ( variableName )
    Gets the absolute URL of the current page.
    Returns:
    the absolute URL of the current page

    Related Assertions, automatically generated:


    storeMouseSpeed ( variableName )
    Returns the number of pixels between "mousemove" events during dragAndDrop commands (default=10).
    Returns:
    the number of pixels between "mousemove" events during dragAndDrop commands (default=10)

    Related Assertions, automatically generated:


    storePrompt ( variableName )
    Retrieves the message of a JavaScript question prompt dialog generated during the previous action.

    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.

    NOTE: under Selenium, JavaScript prompts will NOT pop up a visible dialog.

    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.

    Returns:
    the message of the most recent JavaScript question prompt

    Related Assertions, automatically generated:


    storeSelectedId ( selectLocator, variableName )
    Gets option element ID for selected option in the specified select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the selected option ID in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedId ( selectLocator, pattern )
    • assertNotSelectedId ( selectLocator, pattern )
    • verifySelectedId ( selectLocator, pattern )
    • verifyNotSelectedId ( selectLocator, pattern )
    • waitForSelectedId ( selectLocator, pattern )
    • waitForNotSelectedId ( selectLocator, pattern )

    storeSelectedIds ( selectLocator, variableName )
    Gets all option element IDs for selected options in the specified select or multi-select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    an array of all selected option IDs in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedIds ( selectLocator, pattern )
    • assertNotSelectedIds ( selectLocator, pattern )
    • verifySelectedIds ( selectLocator, pattern )
    • verifyNotSelectedIds ( selectLocator, pattern )
    • waitForSelectedIds ( selectLocator, pattern )
    • waitForNotSelectedIds ( selectLocator, pattern )

    storeSelectedIndex ( selectLocator, variableName )
    Gets option index (option number, starting at 0) for selected option in the specified select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the selected option index in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedIndex ( selectLocator, pattern )
    • assertNotSelectedIndex ( selectLocator, pattern )
    • verifySelectedIndex ( selectLocator, pattern )
    • verifyNotSelectedIndex ( selectLocator, pattern )
    • waitForSelectedIndex ( selectLocator, pattern )
    • waitForNotSelectedIndex ( selectLocator, pattern )

    storeSelectedIndexes ( selectLocator, variableName )
    Gets all option indexes (option number, starting at 0) for selected options in the specified select or multi-select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    an array of all selected option indexes in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedIndexes ( selectLocator, pattern )
    • assertNotSelectedIndexes ( selectLocator, pattern )
    • verifySelectedIndexes ( selectLocator, pattern )
    • verifyNotSelectedIndexes ( selectLocator, pattern )
    • waitForSelectedIndexes ( selectLocator, pattern )
    • waitForNotSelectedIndexes ( selectLocator, pattern )

    storeSelectedLabel ( selectLocator, variableName )
    Gets option label (visible text) for selected option in the specified select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the selected option label in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedLabel ( selectLocator, pattern )
    • assertNotSelectedLabel ( selectLocator, pattern )
    • verifySelectedLabel ( selectLocator, pattern )
    • verifyNotSelectedLabel ( selectLocator, pattern )
    • waitForSelectedLabel ( selectLocator, pattern )
    • waitForNotSelectedLabel ( selectLocator, pattern )

    storeSelectedLabels ( selectLocator, variableName )
    Gets all option labels (visible text) for selected options in the specified select or multi-select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    an array of all selected option labels in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedLabels ( selectLocator, pattern )
    • assertNotSelectedLabels ( selectLocator, pattern )
    • verifySelectedLabels ( selectLocator, pattern )
    • verifyNotSelectedLabels ( selectLocator, pattern )
    • waitForSelectedLabels ( selectLocator, pattern )
    • waitForNotSelectedLabels ( selectLocator, pattern )

    storeSelectedValue ( selectLocator, variableName )
    Gets option value (value attribute) for selected option in the specified select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the selected option value in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedValue ( selectLocator, pattern )
    • assertNotSelectedValue ( selectLocator, pattern )
    • verifySelectedValue ( selectLocator, pattern )
    • verifyNotSelectedValue ( selectLocator, pattern )
    • waitForSelectedValue ( selectLocator, pattern )
    • waitForNotSelectedValue ( selectLocator, pattern )

    storeSelectedValues ( selectLocator, variableName )
    Gets all option values (value attributes) for selected options in the specified select or multi-select element.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    an array of all selected option values in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectedValues ( selectLocator, pattern )
    • assertNotSelectedValues ( selectLocator, pattern )
    • verifySelectedValues ( selectLocator, pattern )
    • verifyNotSelectedValues ( selectLocator, pattern )
    • waitForSelectedValues ( selectLocator, pattern )
    • waitForNotSelectedValues ( selectLocator, pattern )

    storeSelectOptions ( selectLocator, variableName )
    Gets all option labels in the specified select drop-down.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    an array of all option labels in the specified select drop-down

    Related Assertions, automatically generated:

    • assertSelectOptions ( selectLocator, pattern )
    • assertNotSelectOptions ( selectLocator, pattern )
    • verifySelectOptions ( selectLocator, pattern )
    • verifyNotSelectOptions ( selectLocator, pattern )
    • waitForSelectOptions ( selectLocator, pattern )
    • waitForNotSelectOptions ( selectLocator, pattern )

    storeSpeed ( variableName )
    Get execution speed (i.e., get the millisecond length of the delay following each selenium operation). By default, there is no such delay, i.e., the delay is 0 milliseconds. See also setSpeed.
    Returns:
    the execution speed in milliseconds.

    Related Assertions, automatically generated:


    storeTable ( tableCellAddress, variableName )
    Gets the text from a cell of a table. The cellAddress syntax tableLocator.row.column, where row and column start at 0.

    Arguments:

    • tableCellAddress - a cell address, e.g. "foo.1.4"
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the text from the specified cell

    Related Assertions, automatically generated:

    • assertTable ( tableCellAddress, pattern )
    • assertNotTable ( tableCellAddress, pattern )
    • verifyTable ( tableCellAddress, pattern )
    • verifyNotTable ( tableCellAddress, pattern )
    • waitForTable ( tableCellAddress, pattern )
    • waitForNotTable ( tableCellAddress, pattern )

    storeText ( locator, variableName )
    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.

    Arguments:

    Returns:
    the text of the element

    Related Assertions, automatically generated:


    storeTitle ( variableName )
    Gets the title of the current page.
    Returns:
    the title of the current page

    Related Assertions, automatically generated:


    storeValue ( locator, variableName )
    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.

    Arguments:

    Returns:
    the element value, or "on/off" for checkbox/radio elements

    Related Assertions, automatically generated:

    • assertValue ( locator, pattern )
    • assertNotValue ( locator, pattern )
    • verifyValue ( locator, pattern )
    • verifyNotValue ( locator, pattern )
    • waitForValue ( locator, pattern )
    • waitForNotValue ( locator, pattern )

    storeWhetherThisFrameMatchFrameExpression ( currentFrameString, target, variableName )
    Determine whether current/locator identify the frame containing this running code.

    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.

    Arguments:

    • currentFrameString - starting frame
    • target - new frame (which might be relative to the current one)
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    true if the new frame is this code's window

    Related Assertions, automatically generated:

    • assertWhetherThisFrameMatchFrameExpression ( currentFrameString, target )
    • assertNotWhetherThisFrameMatchFrameExpression ( currentFrameString, target )
    • verifyWhetherThisFrameMatchFrameExpression ( currentFrameString, target )
    • verifyNotWhetherThisFrameMatchFrameExpression ( currentFrameString, target )
    • waitForWhetherThisFrameMatchFrameExpression ( currentFrameString, target )
    • waitForNotWhetherThisFrameMatchFrameExpression ( currentFrameString, target )

    storeWhetherThisWindowMatchWindowExpression ( currentWindowString, target, variableName )
    Determine whether currentWindowString plus target identify the window containing this running code.

    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" window. In this case, when the test calls selectWindow, this routine is called for each window to figure out which one has been selected. The selected window will return true, while all others will return false.

    Arguments:

    • currentWindowString - starting window
    • target - new window (which might be relative to the current one, e.g., "_parent")
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    true if the new window is this code's window

    Related Assertions, automatically generated:

    • assertWhetherThisWindowMatchWindowExpression ( currentWindowString, target )
    • assertNotWhetherThisWindowMatchWindowExpression ( currentWindowString, target )
    • verifyWhetherThisWindowMatchWindowExpression ( currentWindowString, target )
    • verifyNotWhetherThisWindowMatchWindowExpression ( currentWindowString, target )
    • waitForWhetherThisWindowMatchWindowExpression ( currentWindowString, target )
    • waitForNotWhetherThisWindowMatchWindowExpression ( currentWindowString, target )

    storeXpathCount ( xpath, variableName )
    Returns the number of nodes that match the specified xpath, eg. "//table" would give the number of tables.

    Arguments:

    • xpath - the xpath expression to evaluate. do NOT wrap this expression in a 'count()' function; we will do that for you.
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    the number of nodes that match the specified xpath

    Related Assertions, automatically generated:

    • assertXpathCount ( xpath, pattern )
    • assertNotXpathCount ( xpath, pattern )
    • verifyXpathCount ( xpath, pattern )
    • verifyNotXpathCount ( xpath, pattern )
    • waitForXpathCount ( xpath, pattern )
    • waitForNotXpathCount ( xpath, pattern )

    storeAlertPresent ( variableName )
    Has an alert occurred?

    This function never throws an exception

    Returns:
    true if there is an alert

    Related Assertions, automatically generated:

    • assertAlertPresent ( )
    • assertAlertNotPresent ( )
    • verifyAlertPresent ( )
    • verifyAlertNotPresent ( )
    • waitForAlertPresent ( )
    • waitForAlertNotPresent ( )

    storeChecked ( locator, variableName )
    Gets whether a toggle-button (checkbox/radio) is checked. Fails if the specified element doesn't exist or isn't a toggle-button.

    Arguments:

    • locator - an element locator pointing to a checkbox or radio button
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    true if the checkbox is checked, false otherwise

    Related Assertions, automatically generated:

    • assertChecked ( locator )
    • assertNotChecked ( locator )
    • verifyChecked ( locator )
    • verifyNotChecked ( locator )
    • waitForChecked ( locator )
    • waitForNotChecked ( locator )

    storeConfirmationPresent ( variableName )
    Has confirm() been called?

    This function never throws an exception

    Returns:
    true if there is a pending confirmation

    Related Assertions, automatically generated:

    • assertConfirmationPresent ( )
    • assertConfirmationNotPresent ( )
    • verifyConfirmationPresent ( )
    • verifyConfirmationNotPresent ( )
    • waitForConfirmationPresent ( )
    • waitForConfirmationNotPresent ( )

    storeCookiePresent ( name, variableName )
    Returns true if a cookie with the specified name is present, or false otherwise.

    Arguments:

    • name - the name of the cookie
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    true if a cookie with the specified name is present, or false otherwise.

    Related Assertions, automatically generated:

    • assertCookiePresent ( name )
    • assertCookieNotPresent ( name )
    • verifyCookiePresent ( name )
    • verifyCookieNotPresent ( name )
    • waitForCookiePresent ( name )
    • waitForCookieNotPresent ( name )

    storeEditable ( locator, variableName )
    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.

    Arguments:

    Returns:
    true if the input element is editable, false otherwise

    Related Assertions, automatically generated:

    • assertEditable ( locator )
    • assertNotEditable ( locator )
    • verifyEditable ( locator )
    • verifyNotEditable ( locator )
    • waitForEditable ( locator )
    • waitForNotEditable ( locator )

    storeElementPresent ( locator, variableName )
    Verifies that the specified element is somewhere on the page.

    Arguments:

    Returns:
    true if the element is present, false otherwise

    Related Assertions, automatically generated:

    • assertElementPresent ( locator )
    • assertElementNotPresent ( locator )
    • verifyElementPresent ( locator )
    • verifyElementNotPresent ( locator )
    • waitForElementPresent ( locator )
    • waitForElementNotPresent ( locator )

    storeOrdered ( locator1, locator2, variableName )
    Check if these two elements have same parent and are ordered siblings in the DOM. Two same elements will not be considered ordered.

    Arguments:

    • locator1 - an element locator pointing to the first element
    • locator2 - an element locator pointing to the second element
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    true if element1 is the previous sibling of element2, false otherwise

    Related Assertions, automatically generated:

    • assertOrdered ( locator1, locator2 )
    • assertNotOrdered ( locator1, locator2 )
    • verifyOrdered ( locator1, locator2 )
    • verifyNotOrdered ( locator1, locator2 )
    • waitForOrdered ( locator1, locator2 )
    • waitForNotOrdered ( locator1, locator2 )

    storePromptPresent ( variableName )
    Has a prompt occurred?

    This function never throws an exception

    Returns:
    true if there is a pending prompt

    Related Assertions, automatically generated:

    • assertPromptPresent ( )
    • assertPromptNotPresent ( )
    • verifyPromptPresent ( )
    • verifyPromptNotPresent ( )
    • waitForPromptPresent ( )
    • waitForPromptNotPresent ( )

    storeSomethingSelected ( selectLocator, variableName )
    Determines whether some option in a drop-down menu is selected.

    Arguments:

    • selectLocator - an element locator identifying a drop-down menu
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    true if some option has been selected, false otherwise

    Related Assertions, automatically generated:

    • assertSomethingSelected ( selectLocator )
    • assertNotSomethingSelected ( selectLocator )
    • verifySomethingSelected ( selectLocator )
    • verifyNotSomethingSelected ( selectLocator )
    • waitForSomethingSelected ( selectLocator )
    • waitForNotSomethingSelected ( selectLocator )

    storeTextPresent ( pattern, variableName )
    Verifies that the specified text pattern appears somewhere on the rendered page shown to the user.

    Arguments:

    • pattern - a pattern to match with the text of the page
    • variableName - the name of a variable in which the result is to be stored.
    Returns:
    true if the pattern matches the text, false otherwise

    Related Assertions, automatically generated:

    • assertTextPresent ( pattern )
    • assertTextNotPresent ( pattern )
    • verifyTextPresent ( pattern )
    • verifyTextNotPresent ( pattern )
    • waitForTextPresent ( pattern )
    • waitForTextNotPresent ( pattern )

    storeVisible ( locator, variableName )
    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.

    Arguments:

    Returns:
    true if the specified element is visible, false otherwise

    Related Assertions, automatically generated:

    • assertVisible ( locator )
    • assertNotVisible ( locator )
    • verifyVisible ( locator )
    • verifyNotVisible ( locator )
    • waitForVisible ( locator )
    • waitForNotVisible ( locator )
  •  apache_maven

    'Integration testing' (sometimes called Integration and Testing, abbreviated I&T) is the activityof software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. [WikiPedia]

     

    I will put Selenium to that JOB. Selenium will allow me to run a set of unit test against a running instance of my application and get a feedback on the quality before delivering the software to a testing team.

    Making any Maven module Selenium enable is really easy, all you have to do is to add to the dependencies section the following

    <dependency>
        <groupId>org.openqa.selenium.client-drivers</groupId>
        <artifactId>selenium-java-client-driver</artifactId>
        <version>0.9.2</version>
        <scope>test</scope>
    </dependency>

    Now you should be able to cut and paste any test cases developed with Selenium IDE into /src/test/java/

    Selenium IDE is a Firefox add-on that records clicks, typing, and other actions to make a test, which you can play back in the browser or export to may different languages: Ruby, Python, Java, PHP, Perl, .Net, JavaScript to name a few. [Learn more]

    The java code is in no way different than regular JUNIT test cases, except that it does not use the latest JUNIT 4.x annotations. You’ll be able to run tests like before (right click Run As Junit)

    package com.waltercedric.maven;
    
    import com.thoughtworks.selenium.SeleneseTestCase; 
    
    public class TestHello extends SeleneseTestCase {
    
      public void setUp() throws Exception {
        setUp(http://localhost/helloworld, "*iexplore");
      }
    
      public void testNew() throws Exception {
        selenium.open("/helloworld/index.xhtml");
        selenium.waitForPageToLoad("30000");
    verifyTrue(selenium.isTextPresent("Are you an existing Customer")); } }

    Some explanations are needed:

    •  
      •  
    • http://localhost/helloworld is the URL of my tomcat container where my web applications will be deployed (port 80)
    • I choose internet explorer as browser as it is nearly always available on any windows pc, Firefox is not far away, use “*firefox” and  firefox.exe has to be in the environment PATH.
    • The Code above assume that a selenium RC server is running at localhost on port 4444, I will show you how to start one later in this post.

    Some remarks about the code above

    You will have to somehow make your own Selenium framework out of the generated code, for obvious reasons,

    • You’ll have soon to support many browser "*iexplore", "*firefox", "*opera" and as such use environment variables or configuration files. I recommend you in that case to use Selenium Grid instead of Selenium RC.
    • You can not let the URL and port of the container fix coded http://localhost/helloworld, this URL may change if you target different runtime. 
    • You may want to reuse some part of the generated code multiple times, in different unit test, (like login/logout stuff), java inheritance, interface, and patterns may arrive sooner or later, even if this is unit test code.

    Selenium test cases or integration tests are meant to be run in phase “integration-test” against a running instance of your application. That is why don’t forget to deploy your application with Maven cargo or run it inside Jetty in Maven phase “pre-integration-test”

    How to use Surefire to run JUnit test in phase “test” and integration tests in phase “integration-test”

    The response is by carefully configuring Surefire and naming your Java packages. The pom.xml below show this trick

    In phase test, test cases with a word integration or selenium are omitted, while in phase “integration-test” they are run.

    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.4.2</version>
        <configuration>
            <argLine> -Xmx512m -DuseSystemClassLoader=true</argLine>
            <skip>false</skip>
            <testFailureIgnore>true</testFailureIgnore>
            <excludes>
                <exclude>**/integration/*</exclude>
                <exclude>**/selenium/*</exclude>
            </excludes>
        </configuration>
        <executions>
            <execution>
                <id>integration-tests</id>
                <phase>integration-test</phase>
                <goals>
                    <goal>test</goal>
                </goals>
                <configuration>
                    <skip>false</skip>
                    <excludes>
                        <exclude>none</exclude>
                    </excludes>
                    <includes>
                        <include>**/integration/*</include>
                        <include>**/selenium/*</include>
                    </includes>
                </configuration>
            </execution>
        </executions>
    </plugin>

    Now it is time to start a selenium server locally or remotely so we can start our newly defined test cases.

    Selenium Remote control

    Selenium Remote Control (RC) is a test tool that allows you to write automated web application UI tests in any programming language against any HTTP website using any mainstream JavaScript-enabled browser.

     

    You can either start a selenium RC server

    • Outside Eclipse, like any java process,
    • Inside Eclipse with a java launcher,
    • Inside Eclipse with Maven and a java launcher.
    • Inside any Maven Phase thank to a plugin XXXXXXXXXXXXX

    I recommend you to install Selenium RC in a dedicated VM (VMWare, Virtual desktop, XEN) and to make it team or enterprise wide. I would always recommend to put Linux at work for such a task, unfortunately Internet Explorer is not running at all on Mac nor Linux.. I recommend you this way to run a shared Selenium server in your infrastructure that can be later access by many continuous build agents.

    Selenium RC is a Java process requiring only 2 jar to properly start, Download and unpack to c:\selenium-server-1.0-beta-2

     

     

     

    Create following in a batch file start.bat, normally all you have to do is to change the first 3 lines

    set JAVA_HOME=c:\jdk1.6
    set FIREFOX_HOME=C:\tools\Firefox3
    set SELENIUM_RC_HOME=c:/selenium-server-1.0-beta-2
    
    set PATH=%PATH%;%FIREFOX_HOME%
    set CLASSPATH=%CLASSPATH%;%SELENIUM_RC_HOME%/selenium-server.jar;%SELENIUM_RC_HOME%/selenium-server-coreless.jar 
    %JAVA_HOME%/bin/java -jar %SELENIUM_RC_HOME%/selenium-server.jar

    If everything run properly, you should see an ugly DOS windows like the one below

     starting.selenium.rc.outside.eclipse

    Pointing the browser to http://localhost:4444 will return an error 403, which is no sign of malfunction, currently Selenium RC has no web GUI.

    seleniumRCtestInBrowser

     

    Start Selenium RC server inside Eclipse

    If you decide to run selenium RC inside Eclipse, you’ll be mainly benefit from:

    • Project sharing and versioning in CVS/SVN,
    • Command line parameters that will start Selenium RC can also be shared,

    Selenium Server in a Maven project/module

    Create a new Maven Project named “SeleniumServer” and copy into its pom.xml the following

    <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
        <modelVersion>4.0.0</modelVersion>
        <groupId>com.waltercedric.maven</groupId>
        <artifactId>SeleniumServer</artifactId>
        <version>0.0.1-SNAPSHOT</version>
        <dependencies>
            <dependency>
                <groupId>org.seleniumhq.selenium.server</groupId>
                <artifactId>selenium-server-coreless</artifactId>
                <version>1.0-beta-2</version>
            </dependency>
            <dependency>
                <groupId>org.seleniumhq.selenium.core</groupId>
                <artifactId>selenium-core</artifactId>
                <version>1.0-beta-2</version>
            </dependency>
        </dependencies>
    </project>

    Create a Java launcher and use org.openqa.selenium.server.SeleniumServer as main class. If you start the launcher, you will see the following in eclipse console

    seleniumRC.started.in.eclipse

     

    Selenium RC is now waiting on port 4444 for Selenium Test case orders.

    You can now run your test case in eclipse like any other test case using Eclipse build in Junit runner.

  • open.qa.logo Selenium is a test tool for web applications. Selenium tests run directly in a browser, just like real users do. It runs in Internet Explorer, Mozilla and Firefox on Windows, Linux, and Macintosh, Safari on the Mac.&160; They have plans to target Safari on the iPhone in some months. The tool is free and available under Apache 2.0.


    • Install the firefox plugin, note the latest version work only in Firefox 2.0 not in 3.0Beta!
    • Install also XPather another Firefox extension, very helpful to get the elements&160; XAPTH in pages.
    • Of course restart Firefox
    • Open either the sidebar (go to menu View, Sidebar, Selenium IDE) or the floating windows
      (go to menu Tools - Selenium IDE)
    • Go to the page where you wan to test something
    • Put the right Base URL (A) and press button (B) when ready
      doYourFirstSeleniumTest
    • You can now act like any user, enter data, change values, click on links
    • When You wan to add a check, you can at any time right click on a HTML element
      (a text, a cell, a button...) to see what selenium is proposing you.
      doYourFirstSeleniumTest.2
    • Not all possibility are proposed...so this is where knowing the element XPATH is helping...
      for more complex check, you can right click on any element and get the XPATH
      doYourFirstSeleniumTest.3 doYourFirstSeleniumTest.4
      now just cut and paste and feed the command (I choose verifytextPresent)
      doYourFirstSeleniumTest.5
    • Don't forget to stop the engine when you are finished or the script may be huge.
    • Into C, You can now cut and paste one or many lines, insert new commands (add more assert)
    • And replay seleniumSecurityImages2 till the&160; bar is green

    &160;

    Attention:

    • Do not abuse XPATH expression as it somehow hard code the previous position of the element in the page.
    • Try to make each test run on its own, do not expect that the test before is successful (so login. test functionality 1, logout)
    • Keep unit test small,
    • Keep all test in a repository (CVS or SVN) or many backup.

    Read also:

  • seleniumhq

    Selenium has various projects that can be combined with each other to create a robust testing environment.

    • Selenium IDE: a Firefox add-on to record and playback tests in Firefox.
    • Selenium Remote Control: a client/server system to control web browsers locally or on other computers, using almost any programming language and testing framework.
    • Selenium Grid: transparently distribute your tests on multiple machines so that you can run your tests in parallel, cutting down the time required for running in-browser test suites. In-browser tests are inherently slow, but since commodity hardware is insanely cheap nowadays there is no excuse for not running all these tests in parallel on multiple machines and dramatically speeding up your feedback cycle. .
    • Selenium Core: JavaScript-based testing system.

    Also there are Selenium projects specifically for Rails, Ruby & Eclipse!

    Today I will show you how to make run some components of Selenium as Windows Services. I am using a Selenium HUB and 4 Selenium RC running all on the same server (while not recommended for performance reasons, it is the easiest setup)

    In this small how to I provide you at the end of the article a ready to use Selenium Grid 0.7 zip file

    Running selenium HUB as an NT service

    The Selenium Hub is in charge of

    • Allocating a Selenium Remote Control to a specific test (transparently)
    • Limiting the number of concurrent test runs on each Remote Control
    • Shielding the tests from the actual grid infrastructure

    Selenium Grid Setup

    1. Download and unzip Selenium Grid.
    2. If you don't have it already, download and install the JDK 
    3. Download Java Service Wrapper (Windows x86 Community Edition) and unzip it.
    4. Create these folders in the Selenium Grid folder: *logs*, *conf*, *bin*. so it look like
    Before After

    selenium-grid-1.0.7
    ├───doc
    ├───examples
    ├───lib
    ├───sample-scripts
    └───vendor

    selenium-grid-1.0.7
    ├───bin
    ├───conf

    ├───doc
    ├───examples
    ├───lib
    ├───logs
    ├───sample-scripts
    └───vendor

    Copy/rename files from the JSW folder to the Selenium Grid folder:

    • \src\conf\wrapper.conf.in to \conf\wrapper.conf
    • \src\bin\App.bat.in to \bin\SeleniumGrid.bat
    • \src\bin\InstallApp-NT.bat.in to \bin\InstallSeleniumGrid-NT.bat
    • \src\bin\UninstallApp-NT.bat.in \bin\UninstallSeleniumGrid-NT.bat
    • \bin\wrapper.exe to \bin\wrapper.exe
    • \lib\wrapper.dll to \lib\wrapper.dll
    • \lib\wrapper.jar to \lib\wrapper.jar

    Now edit the file \conf\wrapper.conf

    Set the location of Java.exe by editing the line

    wrapper.java.command=java

    And making sure to not quote the path even if it has spaces in it


    Replace the  key wrapper.java.classpath.1=... with these three lines:

    wrapper.java.classpath.1=..
    wrapper.java.classpath.2=../lib/selenium-grid-hub-standalone-1.0.7.jar
    wrapper.java.classpath.3=../lib/wrapper.jar


    Change key wrapper.app.parameter.1=+" to:

    wrapper.app.parameter.1=com.thoughtworks.selenium.grid.hub.HubServer

    And finally set up the names/display names for the service:

    wrapper.console.title=Selenium Grid Hub 
    wrapper.ntservice.name=selenium-grid-hub
    wrapper.ntservice.displayname=Selenium Grid Hub
    wrapper.ntservice.description=Central control server for Selenium Grid

    Test your configuration by running the \bin\SeleniumGrid.bat file.

    If it works, you should see Selenium Grid Hub running in the console - one of the the last lines will likely say something about Jetty and you may see some of the Selenium Grid configuration fly past as it's starting up. You can shut it down by pressing Ctrl+C.


    If it's not working, you'll probably see error messages about how the JVM wasn't found (meaning the path to Java is no good) or some other configuration problem. Or the batch file might run and close immediately.

    Once it's running with the SeleniumGrid.bat file, you can install the service by running the InstallSeleniumGrid-NT.bat file.

    To start the service, you can use the command line (net start selenium-grid-hub) or the GUI (Start->Administrative Tools->Services).

    Running multiple selenium RC as NT services

    Selenium Remote Control (RC) is a test tool that allows you to write automated web application UI tests in any programming language against any HTTP website using any mainstream JavaScript-enabled browser.

    Selenium RC comes in two parts. 

    1. A server which automatically launches and kills browsers, and acts as a HTTP proxy for web requests from them.
    2. Client libraries for your favorite computer language.

    Following the same idea, with only some minor changes due to the way selenium RC are started in wrapper.conf

    First install all browsers or only some that you would like to support:

     allBrowser

    Google Chrome, Mozilla Firefox, Apple Safari to name a few, Dont forget that you MUST put them in windows environment variable PATH, so Selenium RC will be able to start them.

    Then create for each browser you would like to support the following directory structure

    Before After

    selenium-grid-1.0.7
    ├───bin
    ├───conf
    ├───doc
    ├───examples
    ├───lib
    ├───logs
    ├───sample-scripts
    └───vendor

    selenium-grid-1.0.7
    ├───bin
    ├───conf
    ├───doc
    ├───examples
    ├───lib
    ├───logs
    ├───rc.chrome
    ├───rc.firefox
    ├───rc.ie
    ├───rc.safari

    ├───sample-scripts
    └───vendor

    Move files around from previous example, so that it look like

    Result
    rc.chrome
    ├───bin
    │       InstallRemoteControl-NT.bat
    │       RemoteControl.bat
    │       UninstallRemoteControl-NT.bat
    │       wrapper.exe

    ├───conf
    │       wrapper.conf

    └───logs

    Here are the settings of wrapper.conf for Google chrome that you need to change across the file, Change all values according to your setup.

    wrapper.ntservice.account=.\selenium
    wrapper.ntservice.password=selenium

    # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=.. wrapper.java.classpath.2=../../lib/selenium-grid-remote-control-standalone-1.0.7.jar wrapper.java.classpath.3=../../lib/selenium-grid-hub-standalone-1.0.7.jar wrapper.java.classpath.4=../../vendor/selenium-server-1.0.3-standalone.jar wrapper.java.classpath.5=../../lib/wrapper.jar # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=com.thoughtworks.selenium.grid.remotecontrol.SelfRegisteringRemoteControlLauncher wrapper.app.parameter.2=-port "5558" wrapper.app.parameter.3=-host "localhost" wrapper.app.parameter.4=-hubURL "http://localhost:4444" wrapper.app.parameter.5=-env "*googlechrome" wrapper.app.parameter.6=-hubPollerIntervalInSeconds "30" wrapper.app.parameter.7=-log "..\logs\chrome.log" wrapper.app.parameter.8=-timeout "15" # Name of the service wrapper.name=selenium-chrome # Display name of the service wrapper.displayname=selenium-chrome # Description of the service wrapper.description=selenium-chrome # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=../../lib

    You get the idea, for every browser, you have to repeat the same procedure. The only difficult point not documented anywhere is that you can not run the browser with the windows local account, you need to use the windows user that has installed the browser or at least has enough right to create a new browser profile. Failing to do it, will throw a null pointer exception while trying to get a new Google Chrome browser session.

    So you must have a valid user under these 2 keys, you can choose what you want

    wrapper.ntservice.account=.\selenium
    wrapper.ntservice.password=xxxxxxxx

    Once it's running with the RemoteControl.bat file, you can install the service by running the InstallRemoteControl-NT.bat file.

    To start the service, you can use the command line (net start selenium-chrome) or the GUI (Start->Administrative Tools->Services).

    Anyway head to the download section and use a ready to use package

     

    How to give the selenium user the permission to "Start a session as a service".

    Thanks to Eric Bouchut for submission

    You need to give the selenium user the permission to start the session as a service, If you don’t do this, the service won't start at least on Windows XP/SP 3.
    Here it is.
    "For the service to start as the selenium user, you need to  give the selenium user the permission to "start a session as a service", as so:

    • Open the Control Panel
    • Click  "Administration Tools"
    • Click "Local Security Settings" (my attempt to translate "Stratégie de Sécurité Locale" in English)
      • In "Local Policies / User Rights Assignment"
      • Double click "Open a session as a service"
        • add the selenium user to the list

    Download

    Original version of selenium-grid-1.0.7-bin.zip if you want to compare the changes i’ve made.

    Ready to use Selenium-Grid 1.0.7 with all the above scripts configured, all the above in one file selenium-grid-1.0.7-bin-modified.NT.services.zip (22MB)

    Happy Integration Testing with Selenium!

  • I put some effort the last few days in this new framework.

    Done:

    • I did document some part of it at http://wiki.waltercedric.com/index.php?title=ContinuousBuildforJoomla
    • TeamCity is installed/configured/documented (windows only)
    • XAMPP is installed/configured/documented (windows only)
    • I also at the same time configured a Puppy Linux VMWare image that will permit to anybody to have a running environment in no time.
    • I am able to unpack all Joomla! versions that are committed in any repository (CVS, SVN, Clearcase)
    • They can be unpacked anywhere on file system (config in setEnv.xml), ideally they are unpacked in the root htdocs of XAMPP
    • Code is committed at Joomla forge in SVN http://joomlacode.org/gf/project/continbuild4j/

    Issues

    Selenium test suite do not accept a baseurl (or only a part of it) so I have a full path like /Joomla1.5.7/installation/index.php in a selenium test case instead of /installation/index.php in test case and baseurl= http://localhost/Joomla1.5.7)

    Architecture

    3rd Party

    • I use antelope for some advance ANT operations: substring, indexof, loop
    • I use selenium java server on port 4444 (default)

    Cluster

    All cluster operations are in cluster.xml these basic functions are

    • cluster.init
      • cluster.remove&160;&160;&160;&160;&160;&160;&160; remove all instances of Joomla! in checkout directory
      • joomla.unpack.all&160;&160;&160; unpack all Joomla! versions that are checked in another SVN root
      • joomla.install.all&160;&160;&160;&160;&160; run the same selenium test case joomla.install.html on all Joomla! instance
      • joomla.remove.all.installation&160;&160; remove all Joomla! installation directories
      • joomla.check.all&160;&160;&160;&160; check all Joomla! installations for correctness
    • cluster.start
    • cluster.remove
    • cluster.stop

    Joomla!

    All Joomla specific operations are in joomla.library.xml

    • Unpack a Joomla! version
    • Remove the installation directory form a version
    • Apply a selenium test suite install.joomla.html that can use the regular Joomla! installer
    • Is also able to do all of the above on all Joomla! versions found (regular expression) in checkout directory

    Selenium

    • All selenium operations are in selenium.xml
    • All test suite and test cases are in /selenium/joomla/

    PHPUnit

    All PHPUnit operation are in phpunit.xml

    Settings

    Settings are in setEnv.xml, in future I will lazy load a file if it exist as environment variable

    &160;

    If you know ANT, the code is quite readable...