canmove, Confirmed users
1,584
edits
(→Testing Locally: restore old content) |
|||
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). | ||
=== | === Testing Locally === | ||
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 | ||
=== Testing on Try Server === | === Testing on Try Server === |