Changes

Prerequisite: Firefox has already been built successfully locally. [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/mach Machmach] is used to run the [[../Tests|Talos tests]] locally. You can run suites of tests or individual tests on their own.

./mach talos-test --suite chromez

./mach talos-test --activeTests tart

Certain talos Talos suites/tests require external pagesets to be downloaded. If pagesets are required, they will be downloaded and extracted automatically when running talos Talos via mach. To disable this automatic pageset downloading, add the 'no-download' argument:

./mach talos-test --suite g1 --no-download

To see a list of available talos Talos suites:

./mach talos-test --print-suites

To see a list of available talos Talos tests:

./mach talos-test --print-tests

./mach talos-test --help

find . | xargs touch == Try Server == To run talos tests on the try server, you just simply push to try as normal, specifying that you want to run Talos tests. It is highly recommended that you use [http://trychooser.pub.build.mozilla.org/ trychooser] to build your try server syntax (helpful hint for using trychooser: in the list of talos suites available you can hover over any one of the suites, and a list of tests included in that suite will be displayed).

== Try server ==To run all of Talos tests on the talos tests as part of your try pushserver, you just add "-t all" simply push to the end of your try syntax. To run a single talos suite as part of your try pushnormal, just add "-t <name of suite>" specifying that you want to run Talos tests. It is highly recommended that you use [http://trychooser.pub.build.mozilla.org/ trychooser] to build your try server syntax (i.e. "-t g1"helpful hint for using trychooser: in the list of Talos suites available you can hover over any one of the suites, and a list of tests included in that suite will be displayed).

To turn on [[TestEngineering/Performance/run all of the Talos/Profiling|profiling]] tests as part of your talos tests on trypush, just add "mozharness: --spsProfilet all" to the end of the your try syntax. To run a single Talos suite as part of your try push, just add "-t <name of suite>" to your try syntax (i.e. "-t g1 mozharness: --spsProfile"). There is an option to do this in trychooser.

When viewing To turn on [[../Profiling|profiling]] as part of your talos tests on try server results on Treeherder, look for the group names 'T' and 'Tadd "mozharness: --e10s'. Click on the green symbol corresponding spsProfile" to the talos suite name, and then click on end of the 'Performance' tab below try syntax (i.e. "-t g1 mozharness: --spsProfile"). There is an option to see the test resultsdo this in trychooser.

If youWhen viewing your Talos try server results on Treeherder, look for the group names 'T're curious about and 'T-e10s'. Click on the hardware we usegreen symbol corresponding to the Talos suite name, here is a [[../Misc#Hardware_Profile_of_machines_used_in_automation|description of and then click on the specs]]. You can also refer 'Performance' tab below to see the [[ReferencePlatforms#Build_Reference_Platforms|test reference platforms]] documentationresults.

= Are my Talos results OK? =The best way to answer this question is to push to try server and compare the performance of your push against a baseline, using Perfherder (it is recommended hitting retrigger a few times to get at least 5 data points for each test). After pushing to try with talos Talos tests enabled, you will receive an email with a link to Perfherder where you can compare your results. Make sure you look at the different platforms.