Changes

'''NOTE''': We currently test all releases for all locales starting from Gecko 38. This should be reduced in a follow up bug (XXX: To be filed).

If I didn't set --update-channel, it would update to 38.0.5 instead of the latest beta on 39.

= Run the tests Setup steps = hg clone http://hg.mozilla.org/build/mozharness cd mozharness python scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg update_testsreleases/mozilla-{beta,release}.py cd testing/mozharness

XXX: This still needs to be implemented.You can use append --update-direct-only and --update-fallback-only to only run one of the two.

python scripts/firefox_ui_updates.py --cfg generic_releng_config.py --cfg update_tests/mozilla-{beta,release}.py --this-chunk=1 --total-chunks=10 To see what will would run on which chunk you can use --dry-run True. Remember to read about how to run locally in this doc.

There is a config per release branchgeneric_releng_config.You can see them in [http://hg.mozillapy with basic values to run inside of Release Engineering's infrastructure.org/build/mozharness/file/default/configs/update_tests|configs/update_tests]. The only two values that are specified are:* the tools update verify There is also platform spefic config (e.g. mozBetathink 32-firefoxbit vs 64-linux64.cfgbit on the same host)** You can to set the MINIDUMP_STACKWALK variable for crash dumps (see them all in [https://hg.mozilla.org/buildreleases/tools/filemozilla-aurora/defaultrev/release/updates|heree48ae21ed414 patch]).* There is also the developer_config.py which [https://github.com/mozilla/firefox-ui-tests|firefox_ui_tests] branch allows you to check out (erun the harness on your local machine.g. mozilla-beta)

The mozharness script takes care of setting up the environment, checking out repositories, updating to the right branches , setting the right environment variables and execute the tests.

Internally, we call the [http://hg.mozilla.org/build/mozharness/file/2a5172fb2335/scripts/firefox_ui_updates.py#l247|firefox_ui_update] binary that gets generated from the firefox ui tests repository (the runner is defined in [https://github.com/mozilla/firefox-ui-tests/blob/master/firefox_ui_harness/runners/update.py#L53|here]).

The A basic call to the binary looks similar to this:XXX: Double check this

'''NOTE:''' If any tests fail in the jobs running for you see a failure on the releasesrelease logs, you will be able to see also have printed out '''the exact command you need to execute on your local machinerun'''. Here's a sample command from one of the release jobs: # This is a sample command for running Linux64 jobs python scripts/scripts/firefox_ui_updates.py --cfg generic_releng_config.py \ --cfg generic_releng_linux64.py --firefox-ui-branch mozilla-beta \ --update-verify-config mozBeta-firefox-linux64. It will ask cfg \ --tools-tag FIREFOX_40_0b7_RELEASE_RUNTIME --total-chunks 6 \ --this-chunk 1 --build-number 1 All you would have to do:* copy a command from a log (use sample command above)* append --installer-url and have cfg developer_config.py to run it locally on your machine* remove one of the two "scripts/" in the right options command The code has been optimized to userun on your local machine.

== --installer-url/--installer-path Without using releng configs ==

--installer-url:

 The update tests allow you tospecify some more options. Please see all the --update-* options of the