Changes

Jump to: navigation, search

Auto-tools/Projects/Marionette update tests

140 bytes added, 18:28, 1 May 2015
manual steps and developer machine
** This is dumped into verify.sh's output if a test does not pass
= Run by hand on your local machine =You don't need Besides verify.sh , you have marionette_testing.sh which allows you to run a single locale.
If you have not run this: ./verifymarionette_testing.sh config_fileit will enable developer options for you can create the venv like this: ../common/setup_firefox_ui_updates.sh --developer-mode venv ./verify.sh $options --marionette $config_file
You can use --keep-venv and --developerdont-mode for this scriptclear-chache if you would like to.
After you run verify.sh or setup_firefox_ui_updates.sh, you can run the tests like this== Run step-by-step ==Setup: virtualenv --no-site-packages venv source venv/bin/activate (For Windows "Scripts" instead of "bin") pip install --no-index --find-links http://pypi.pub.build.mozilla.org/pub -r ../firefox_ui_updates_requirements.txt
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
NOTE: By default, a gecko.log file is generated to remove noise from running firefox-ui-update. Read the help message to know how to adjust it if need be.
 
NOTE: On Linux loaners you need to set DISPLAY=:2
For beta and release builds which have not yet been released, you need the right update channel:
Armenzg
Confirm
3,990
edits
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1071534"

Navigation menu