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

From MozillaWiki
Jump to navigation Jump to search
(Replaced content with "Since November 2016, we are no longer actively using or maintaining a Selenium Grid instance.")
 
(141 intermediate revisions by 9 users not shown)
Line 1: Line 1:
== Startup ==
Since November 2016, we are no longer actively using or maintaining a Selenium Grid instance.
=== Starting the Hub ===
* VNC into or use Screen, and go on qa-selenium.mv.mozilla.com,
* start a screen session -> screen -S selenium_grid_hub
* cd moz-grid-config
* start the hub -> ./launchHub.sh
 
=== Starting RCs ===
 
== Shutdown ==
=== Shutdown the Hub ===
=== Shutdown the RCs ===
 
== Upgrading ==
=== Upgrading Jenkins ===
# Load http://qa-selenium.mv.mozilla.com:8080/
# 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 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
 
== Selenium Grid ==
=== Adding a new environment ===
* Add the browser, alias, and path to https://github.com/mozilla/moz-grid-config/blob/master/grid_configuration.yml
 
== Moz-Grid-Config ==
 
* [https://github.com/mozilla/moz-grid-config moz-grid-config]
 
== References ==
 
* [http://qa-selenium.mv.mozilla.com:8080/ Grid Admin Console]
* [http://qa-selenium.mv.mozilla.com:4444/console Grid Hub Snapshot]
* [https://github.com/mozilla/moz-grid-config Github] config snapshot

Latest revision as of 15:10, 1 November 2016

Since November 2016, we are no longer actively using or maintaining a Selenium Grid instance.