Confirmed users
137
edits
QA/Execution/Web Testing/Automation/Selenium Grid: Difference between revisions
QA/Execution/Web Testing/Automation/Selenium Grid (view source)
Revision as of 13:14, 8 December 2011
, 8 December 2011no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
== Selenium Grid == | == Selenium Grid == | ||
=== moz-grid-config === | |||
* moz-grid-config is our project for managing the Selenium Grid hub, nodes and configuration of them. It packages it all together so that starting the grid is simple a matter of running 'ant launch-hub' or 'ant launch-node'. | |||
* moz-grid-config requires Git for checking out the project and Apache ant and Java for running the grid and nodes. | |||
* moz-grid-config is configured for Mozilla's architecture but it can be used locally by changing the hub.host and node.configuration in default.properties to represent your local settings. You may also need to change the path to your browser binaries in the json files. | |||
* [https://github.com/mozilla/moz-grid-config moz-grid-config] | |||
=== Starting the Hub === | === Starting the Hub === | ||
* VNC into or use Screen, and go on qa-selenium.mv.mozilla.com, | * VNC into or use Screen, and go on qa-selenium.mv.mozilla.com, | ||
| Line 10: | Line 20: | ||
* start a screen session -> screen -S selenium_rc | * start a screen session -> screen -S selenium_rc | ||
* cd moz-grid-config | * cd moz-grid-config | ||
* start the | * start the node -> ant launch-node | ||
=== Shutdown === | === Shutdown === | ||
* Use <control> c | * Use <control> c | ||
=== Architecture === | === Architecture === | ||
| Line 86: | Line 81: | ||
* Fork the repo, do a pull request, merge to master (<- please correct if wrong) | * Fork the repo, do a pull request, merge to master (<- please correct if wrong) | ||
== | == Jenkins == | ||
=== Starting Jenkins === | |||
* VPN in via Mozilla-MV to http://qa-selenium.mv.mozilla.org:8080/, 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, we launch as follows: | |||
java -jar -Xms2g -Xmx2g -XX:MaxPermSize=512M -Xincgc ~/Desktop/jenkins.war | |||
=== Upgrading Jenkins === | |||
# Load http://qa-selenium.mv.mozilla.com:8080/ (must be on VPN) | |||
# Click on [http://qa-selenium.mv.mozilla.com:8080/manage "Manage Jenkins"] - http://qa-selenium.mv.mozilla.com:8080/manage | |||
# Click on [http://qa-selenium.mv.mozilla.com:8080/quietDown "Prepare for Shutdown"] - http://qa-selenium.mv.mozilla.com:8080/quietDown | |||
# VNC into qa-selenium.mv.mozilla.com and go to the Terminal window and CTRL+C (you'll see Java processes shutting down) | |||
# Now, either arrow-up, or explicitly do "java jar -Xms2g -Xmx2g -XX:MaxPermSize=512M -xincgc jenkins.war" -- this should restart Jenkins, and be it! It'll take some time for it to fully come back up, and for qatestbot to join #mozwebqa | |||
== Mac OS X-Hostname Setting (shamelessly copied, verbatim, from http://budporter.net/?p=47) == | == Mac OS X-Hostname Setting (shamelessly copied, verbatim, from http://budporter.net/?p=47) == | ||