Buildbot/Talos/Running: Difference between revisions

Undo revision 732205 by Mbrubeck (talk)
(→‎Testing Locally: restore old content)
(Undo revision 732205 by Mbrubeck (talk))
Line 11: Line 11:
If you are making changes to talos obviously running the tests locally will be the first step.  The next logical step is to run the tests on Try server (try: -b o -p all -u none -t all).
If you are making changes to talos obviously running the tests locally will be the first step.  The next logical step is to run the tests on Try server (try: -b o -p all -u none -t all).


=== Using a local Talos repo ===
=== Testing Locally ===
 
If you are making changes to Talos itself, you will want to test your changes by building and running your local copy of the Talos source code:
 
'''Clone Talos:'''
 
hg clone http://hg.mozilla.org/build/talos
 
'''Run the [http://hg.mozilla.org/build/talos/file/default/INSTALL.py install script]''':
 
cd talos
python INSTALL.py
# (Ignore errors like "fatal error: 'yaml.h' file not found. To get rid of this error message you can download and install PyYAML from http://pyyaml.org/wiki/PyYAML but it is not necessary.
 
The INSTALL.py script creates a [https://developer.mozilla.org/en/Python/Virtualenv Virtualenv] in the same directory as 'INSTALL.py' and installs the talos [https://developer.mozilla.org/en/Python#Python_packaging python package] into the virtualenv, including its [https://wiki.mozilla.org/Auto-tools/Projects/MozBase MozBase dependencies] via 'python setup.py develop'. ''(Alternatively, you can perform these steps yourself.)''
 
'''Activate the virtualenv:'''
 
''(on windows):''
Scripts\activate.bat
 
''(on osx/linux)'':
. bin/activate
 
'''Unpack a copy of firefox somewhere''' (for this example, we'll use `which firefox` as if firefox was on your path).
 
'''Set up a webserver''' if you're not using the '--develop' flag. (WE STRONGLY RECOMMEND USING THE --develop FLAG.)
 
* Set up apache or similar webserver to have http://localhost -> the talos subdirectory of the talos checkout.
* Alternatively you can use the --develop flag to PerfConfigurator which configures to use a python webserver, [https://github.com/mozilla/mozbase/tree/master/mozhttpd mozhttpd], as shown below
 
'''Run the tests''':


Testing locally involves running some subset of the Talos tests on
Testing locally involves running some subset of the Talos tests on
desktop and possibly mobile.  Obviously not all permutations of tests
desktop and possibly mobile.  Obviously not all permutations of tests
and the ways of running them can be tried, so common sense should be
and the ways of running them can be tried, so common sense should be
used as to what is run.   
used as to what is run.  You may also want to run Talos' internal
unittests: http://hg.mozilla.org/build/talos/file/tip/tests


You should tailor your choice of tests to pick those that cover what
You should tailor your choice of tests to pick those that cover what
Line 54: Line 24:
baseline might be:
baseline might be:


  # refer to [https://wiki.mozilla.org/Buildbot/Talos#Running_locally_-_Source_Code running locally] for more details
   talos -n -d -a ts:tsvg -e `which firefox` --develop --datazilla-url output.json --mozAfterPaint
   talos -n -d -a ts:tsvg -e `which firefox` --develop --datazilla-url output.json --mozAfterPaint
You may also want to run Talos' internal unit tests: http://hg.mozilla.org/build/talos/file/tip/tests


=== Testing on Try Server ===
=== Testing on Try Server ===
canmove, Confirmed users
1,584

edits