TestEngineering/Performance/Talos/Development: Difference between revisions

TestEngineering/Performance/Talos/Development (view source)

Revision as of 11:26, 13 August 2019

521 bytes removed , 13 August 2019

no edit summary

Davehunt

Confirmed users

2,177

edits

@@ Line 1: / Line 1: @@
 = Environment =
 {{warning|Talos currently requires Python 2.7}}
 Prerequisites: Local clone of mozilla-central and a successful [https://developer.mozilla.org/en-US/docs/Simple_Firefox_build mozilla-central Firefox build] completed.
-On Linux, setuptools installed:
-  apt-get install python-setuptools
-Not required on Windows. For other operating systems see [https://pypi.python.org/pypi/setuptools setuptools].
-On Linux, virtualenv installed:
-  pip install virtualenv
-Not required on Windows. For other operating systems see [http://www.virtualenv.org/en/latest/virtualenv.html#installation virtualenv].
-Setup Talos (linux):
-  cd mozilla-central/testing/talos
-  virtualenv .
-  . bin/activate
-  python setup.py develop
-Setup talos (Windows with mozilla-build):
-  cd mozilla-central/testing/talos
-  python INSTALL.py  # only required once or after updating mozilla-build
-  source Scripts/activate  # you can also use '.' (dot) instead of 'source'
 = Testing your patch locally =
-Testing locally involves running some subset of the Talos tests on desktop and possibly mobile.  Obviously not all permutations of tests and the ways of running them can be tried, so common sense should be used as to what is run. You may also want to run the [http://hg.mozilla.org/build/talos/file/tip/tests Talos unittests].
+Testing locally involves running some subset of the Talos tests on desktop and possibly mobile.  Obviously not all permutations of tests and the ways of running them can be tried, so common sense should be used as to what is run. You may also want to run the [https://searchfox.org/mozilla-central/source/testing/talos/talos/unittests Talos harness tests].{{todo|document how to run Talos harness tests}}
 You should tailor your choice of tests to pick those that cover what you've changed programmatically, but in general you should probably run at least one startup test and one pageloader test. A good baseline might be the 'tresize' and 'tsvgx' test suites.
+{{warning|The following is currently broken. Once {{bug|1573429}} is resolved we can update this to use {{code|mach talos-test}}}}
 Run the tests from mozilla-central/testing/talos (with the venv activated, as noted above):