QA/Execution/Web Testing/Automation/Selenium Grid

Selenium Grid

moz-grid-config

moz-grid-config is a project for managing our Selenium infrastructure. It includes the latest version of Selenium that we're using, and a mechanism for starting the hub/nodes. You can find documentation on moz-grid-config at the github project page.

Starting the hub

1. Connect to qa-selenium.mv.mozilla.com
2. From a terminal (you can use SSH, VNC, or Screen):

   cd ~/moz-grid-config
   ant launch-hub

Starting nodes

1. Connect to the appropriate machine.
2. From a terminal (you can use SSH, VNC, or Screen):

   cd ~/moz-grid-config
   ant launch-node

Shutdown

• Terminate the process using CTRL+C

Architecture

• qa-selenium.mv.mozilla.com (10.250.1.143)
  • Mac Mini; 2.66 Ghz Intel Core 2 Duo; 8 GB
  • Mac OS X 10.6.8
  • Jenkins (dashboard)
  • Selenium Grid hub (console)
• qa-selenium2.mv.mozilla.com (10.250.1.167) -- NO LONGER USED
• qa-selenium3.mv.mozilla.com (10.250.1.196)
  • Mac Mini; 2.4 Ghz Intel Core 2 Duo; 4 GB
  • Mac OS X 10.6.8
  • VM: Windows 7 Professional (10.250.7.78)
• qa-selenium4.mv.mozilla.com (10.250.1.197)
  • Mac Mini; 2.4 Ghz Intel Core 2 Duo; 4 GB
  • Mac OS X 10.6.8
  • VM: Windows 7 Professional (10.250.4.68)
• qa-selenium5.mv.mozilla.com (10.250.1.222)
  • Mac Mini; 2.66 Ghz Intel Core 2 Duo; 8 GB
  • Mac OS X 10.6.8
  • VM: Windows 7 Professional (10.250.5.71)
• qa-selenium6.mv.mozilla.com (10.250.1.221)
  • Mac Mini; 2.53 Ghz Intel Core 2 Duo; 4 GB
  • Mac OS X 10.6.8
  • VM: Windows 7 Professional (10.250.2.244)
• qa-selenium7.mv.mozilla.com (10.250.1.9)
• Tegra 2 Boards
  • 10.250.4.149

We have several Mac Minis running Selenium nodes, integrated via Jenkins Continuous Build Integration and Selenium Grid. All machines can be VNC'ed into from within the MV-Office Intranet (VPN if offsite). In order to start the entire system (Jenkins, Selenium Grid, and all VMs with Selenium RCs), ensure that all the Mac Minis are powered on and logged in.

Node configuration

Since Selenium 2.14.0 was released and allowed both RC and WebDriver nodes to co-exist each node runs the same configuration of browser nodes.

Firefox version policy

Due to rapid release, we have adopted the following policy for Firefox versions available on our Selenium infrastructure:

• Nightly
• Aurora
• Beta
• Currently supported Firefox release(s)
• One previous major Firefox release

Selenium RC

• Firefox 3.6 (x5)
• Firefox 7 (x5) - to be removed
• Firefox 8 (x5)
• Firefox 9 (x5)
• Firefox 10 (x5)
• Firefox Beta (x5)
• Aurora (x5)
• Nightly (x5)
• Internet Explorer 8 (x1)

WebDriver

Instances are currently set to 1 due to issues with focus.

• Firefox 3.6 (x1)
• Firefox 7 (x1) - to be removed
• Firefox 8 (x1)
• Firefox 9 (x1)
• Firefox 10 (x1)
• Firefox Beta (x1)
• Aurora (x1)
• Nightly (x1)
• Internet Explorer 8 (x1)

Adding a new browser environment

Configuration

You will need to fork and clone from the moz-grid-config github repository and work on a new branch.

1. Add the browser, alias, and path to grid_configuration.yml
2. Add the browser, binary and details to the JSON configuration files
3. Submit a pull request to the main github repository from your branch

Hub/Nodes

1. Prepare Jenkins for shutdown - this will allow all currently running jobs to finish, but will not start any new jobs.
2. Once no jobs are running, shutdown the Selenium Grid hub
3. Pull in the latest changes from moz-grid-config
4. Start the Selenium Grid hub
5. For each Selenium node:
   1. Shutdown the Selenium node
   2. Pull in the latest changes from moz-grid-config
   3. Install the appropriate browser for the new environment
   4. Start the Selenium node

Installing Firefox

• All new browsers should be installed with the version number in the path so that moz-grid-config can always find them!
• Download Firefox binaries from http://releases.mozilla.org/pub/mozilla.org/firefox/releases/

Mac OS X

1. Download the appropriate DMG file
2. Open the disc image (DMG) and drag Firefox to the desktop
3. Rename Firefox to include the version number (e.g. 'Firefox 10.app')
4. Move the file from the desktop into the Application folder

Windows

1. Download the appropriate MSI file
2. Run the Firefox installer and select custom install
3. Change the default install path to include the version number (e.g. 'C:\Program Files\Mozilla Firefox 10\')
4. Complete the install and uncheck 'set as default browser'

Jenkins

Starting Jenkins

1. VPN in via Mozilla-MV to qa-selenium.mv.mozilla.org
2. Look for an existing Terminal/Console window with a Jenkins process
   • If there's one there, you should just be able to cursor-up and type Enter/Return to launch
   • If not, launch as follows:

   java -jar -Xms2g -Xmx2g -XX:MaxPermSize=512M -Xincgc ~/Desktop/jenkins.war

Upgrading Jenkins

1. Open the Jenkins dashboard (must be on VPN)
2. Click on Manage Jenkins
3. Click on Prepare for Shutdown
4. VNC into qa-selenium.mv.mozilla.com and go to the Terminal window and CTRL+C (you'll see Java processes shutting down)
5. Start Jenkins

Jenkins Backup

Web QA is using the thinBackup (https://wiki.jenkins-ci.org/display/JENKINS/thinBackup) plugin to perform scheduled (currently daily) backups of the Jenkins XML files that store the Jenkins system config, jobs, plugins installed.

ThinBackup saves the backup to FS2 in the folder /public/QA/WebQA/Jenkins/

There is an unscheduled backup of the Plugins in this folder too but be aware these plugins may be out of date.

Restoring procedure

While thinBackup does backup a list of plugins used it cannot install them while restoring the Jenkins config and jobs. It will restore all of the settings that were used by the plugin but until the plugin is installed they won't be visible or active.

The work around to this is to install them manually before performing the restore. If a plugin is no longer available or obsolete then its settings may be lost.

Steps to restore WebQA's Jenkins instance:

1. On the new/recovered server install and start a clean Jenkins instance.
2. Open up that Jenkins instance and install thinBackup
3. On the thinBackup settings page set the Backup directory to point to the fs2 directory.
4. From the FS2 directory open the backed up list of plugins installedPlugins.xml in a text editor.
5. In Jenkins install each plugin listed in the XML file. The first string in the <entry> matches the plugin-id. The plugin-id is listed in the information matrix at the top of the plugin's homepage (eg https://wiki.jenkins-ci.org/display/JENKINS/thinBackup)
6. Go back to thinBackup settings page and perform the thinBackup restore procedure.
7. Restart Jenkins.
8. Check that the jobs have retained the plugin settings.

NB if job settings have been lost then the plugin may not have been installed or be a different version.

Setting hostname on Mac OS X

Shamelessly copied from http://budporter.net/?p=47

If you are running a version of OSX prior to 10.5, then look in /etc/hostconfig for the HOSTNAME= parameter and set it to be the FQDN (Fully Qualified Domain Name) that you want to use. So, for host foo located in the domain bar.com, the entry would be as follows:

   HOSTNAME=foo.bar.com

For OSX 10.5, /etc/hostconfig is being deprecated. There are a couple of preferred methods to do this in 10.5:

   sudo hostname -s foo.bar.com

or:

   sudo scutil –set HostName foo.bar.com

You can verify the change by issuing the following command:

   hostname

The output will display the FQDN of the computer.

Registering the Tegra Board to the Selenium Grid

Install and open the WebDriver Android (android-server-x.xx.apk where x.xx is current version) application on the Tegra board. Install the FlynnID python package on your computer. Open your terminal and type the following command

 flynnid --hubhost=[HUBIP] --hubport=4444 --nodehost=[NODEIP] --nodeport=8080 --browsername=browser --platform=ANDROID

where HUBIP is the hostname or IP address of the Selenium Grid and NODEIP is the hostname or IP address of the Tegra board

If everything goes right, you should see

  Registering the node to hub: http://qa-selenium.mv.mozilla.com:4444/grid/register
  Success!

You can check to see if the node is running by visiting the following url in your browser

  http://[NODEIP]:[NODEPORT]/wd/hub/static/resource/hub.html

where NODEIP is the hostname or IP address of the Tegra board and NODEPORT is the port the node is listening, the default is 8080.

References

• Jenkins dashboard
• Selenium Grid console
• moz-grid-config on github