TestEngineering/Web/Automation/Gaia UI Testing: Difference between revisions

TestEngineering/Web/Automation/Gaia UI Testing (view source)

905 bytes added , 5 December 2013

Confirmed users

137

edits

@@ Line 104: / Line 104: @@
 You can find the executables for B2G desktop at:
 * [https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/ Master]
 * [https://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/ v1.2] - look for the ones prefixed with mozilla-b2g26_v1_2, e.g. [https://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-b2g26_v1_2-macosx64_gecko/ mozilla-b2g26_v1_2-macosx64_gecko]
+Running like Travis locally.
+There are two steps to running tests like Travis locally; install (downloads Gecko and builds Gaia) and run tests.
+The tests must be run from the gaia/ root directory.
+When running locally we need to be aware of 3 things:
+. The travis install script will not download a new Gecko if one already exists. The solution is to "rm -rf b2g" and "rm -rf profile" to remove the artifacts that the install script creates
+. The install script will install the Python packages at global level. The solution is to remove "sudo" from line 5 of the install script.
+. I forgot wot this one woz but for some reason in my mind I thought there were 3
+The install script is run by:
+> tests/travis/gaia-ui-tests/install
+To run the tests, modify the script file to include the command line options you need. All normal command line options are valid.
+> tests/travis/gaia-ui-tests/script
 = Keeping Branches in Sync with Master =