QA/Execution/Web Testing/Automation/Selenium Grid: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 8: Line 8:
We have several Mac minis running as Selenium nodes and 6 VMs running Windows nodes in our data-center.
We have several Mac minis running as Selenium nodes and 6 VMs running Windows nodes in our data-center.


=== Mac OS X ===
=== Mac OS X Nodes ===
* '''selenium'''.qa.mtv2.mozilla.com (10.252.73.143)
* '''selenium'''.qa.mtv2.mozilla.com (10.252.73.143)
** Mac Mini; 2.7 Ghz Intel Core i7; 8 GB  
** Mac Mini; 2.7 Ghz Intel Core i7; 8 GB  
Line 24: Line 24:
** Mac OS X 10.7.4, 2.5 GHz Intel Core i5; 4GB 1067 MHz DDR3
** Mac OS X 10.7.4, 2.5 GHz Intel Core i5; 4GB 1067 MHz DDR3


=== Windows ===
=== Windows Nodes ===
* '''selenium1'''.qa.scl3.mozilla.com (10.22.73.149)
* '''selenium1'''.qa.scl3.mozilla.com (10.22.73.149)
** Windows 7, 8 GB RAM, 2 cores, 150GB disk
** Windows 7, 8 GB RAM, 2 cores, 150GB disk
Line 38: Line 38:
** Windows 7, 8 GB RAM, 2 cores, 150GB disk
** Windows 7, 8 GB RAM, 2 cores, 150GB disk


=== Starting Mac OS X nodes ===
=== Starting Mac OS X Nodes ===
Connect to the appropriate machine, and execute the following from a terminal (you can use SSH or VNC):
Connect to the appropriate machine, and execute the following from a terminal (you can use SSH or VNC):


Line 44: Line 44:
     ant launch-node
     ant launch-node


=== Starting Windows nodes ===
=== Starting Windows Nodes ===
We use the [http://msysgit.github.io msysgit] tool on Windows. Connect to the appropriate machine using Remote Desktop, start the MsysGit tool on the desktop, and run the following commands:
We use the [http://msysgit.github.io msysgit] tool on Windows. Connect to the appropriate machine using Remote Desktop, start the MsysGit tool on the desktop, and run the following commands:


Line 52: Line 52:
We need the <code>-autoproxy</code> helper because the these nodes run through a proxy.
We need the <code>-autoproxy</code> helper because the these nodes run through a proxy.


=== Stopping nodes ===
=== Stopping Nodes ===
Terminate the process using Ctrl+C.
Terminate the process using Ctrl+C.


Line 122: Line 122:
== Updating ==
== Updating ==
Before updating the Grid we need to test locally with the latest Firefox and Selenium versions.
Before updating the Grid we need to test locally with the latest Firefox and Selenium versions.
# You will need to fork and clone from the [https://github.com/mozilla/moz-grid-config moz-grid-config github repository] and work on a new branch (latest-version) (see [[#Configuration|Configuration]].
# You will need to fork and clone from the [https://github.com/mozilla/moz-grid-config moz-grid-config github repository] and work on a new branch (latest-version).
#* Install the latest Firefox version on your local machine
#* Install the latest Firefox version on your local machine
#* Change the Selenium version to be the latest (in default.properties file), then it will be downloaded automatically when starting the hub/node.  
#* Change the Selenium version to be the latest (in <code>default.properties</code> file), then it will be downloaded automatically when starting the hub/node.  
#* Update the JSON files for your operating system - add the latest browser, binary and details. (for both hub and nodes)
#* Update the JSON files for your operating system - add the latest browser, binary and details. (for both hub and nodes)
#* Update the Selenium client using "pip install -r requirements.txt". Start the hub and node and start testing.
#* Update the Selenium client using <code>pip install -r requirements.txt</code>. Start the hub and node and start testing.
# After changes are merged into the main GitHub repository, move the main Grid to run on "latest-version" branch.
# After changes are merged into the main GitHub repository, move the main Grid to run on "latest-version" branch.
# Once testing on the main Grid instance is successful, merge the latest-version branch into master and switch back to the master branch on the hub and nodes.
# Once testing on the main Grid instance is successful, merge the latest-version branch into master and switch back to the master branch on the hub and nodes.
Confirmed users
2,177

edits

Navigation menu