The tests are being integrated inside of [https://github.com/mozilla/build-tools/blob/master/release/updates/verify.sh verify.sh] (not yet).
= Support =
Only Gecko 38 and higher is supported.
= Run the tests =
The script that is used by Release Engineering can be run like this:
hg clone http://hg.mozilla.org/build/tools
cd release/updates
./verify.sh --marionette mozBeta-firefox-linux64.cfg # Config depends on your host OS
This script will create the following directories:
* cache - where downloaded installers are store to speed up future downloads
* downloads - temporary dir where installers being tested on a specific iteration
* venv - where the dependencies of firefox-ui-tests are installed
You can also use --keep-env and --dont-clear-cache to prevent blowing up the dirs every time.
To run a small set of tests, simply grab one of the lines from the configs.
You can also reduce the list of locales in that line.
Two text files are generated:
* short_log.txt - it contains the output of firefox-ui-update
* joint_output.txt - it contains the output of gecko intertwined withe firefox-ui-update
** This is dumped into verify.sh's output if a test does not pass
= Run by hand =
You don't need verify.sh to run a single locale.
If you have not run ./verify.sh you can create the venv like this:
../common/setup-marionette.sh venv
After you run verify.sh or setup-marionette.sh, you can run the tests like this:
source venv/bin/activate (For Windows "Scripts" instead of "bin")
Download the binary you want to try:
wget ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2015-04-20-03-02-04-mozilla-central/firefox-40.0a1.en-US.win32.installer.exe
Run the two tests:
firefox-ui-update --installer firefox-40.0a1.en-US.win32.installer.exe
For beta and release builds which have not yet been released, you need the right update channel:
= Failure modes =