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

Line 181: Line 181:
The output will display the FQDN of the computer.
The output will display the FQDN of the computer.
== Updating the Grid (step by step) ==
== Updating the Grid (step by step) ==
Before updating the Grid we need to test locally with the latest FF version and the latest selenium version.
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) (see [[#Configuration|Configuration]].
##Install the latest Firefox 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 default.properties file), then it will be downloaded automatically when starting the hub/node.  
##Update the OS json files, add the latest browser, binary and details. (both for hub and node)
## Update the JSON files for your operating system - add the latest browser, binary and details. (for both hub and nodes)
##Make sure that you also update Selenium for your local project environment with "pip install -r requirements.txt". Start the hub and node and start testing.
## Update the Selenium client using "pip install -r requirements.txt". Start the hub and node and start testing.
#After changes were merged into the main github repository, it's time to move the 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.
*The process is the same as it was doing this locally, but now we have to pull the latest changes from moz-grid-config and switch to the "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.
*Process explained in [[#Hub/Nodes|Hub/Nodes]]


== References ==
== References ==
Confirmed users
2,177

edits