Confirmed users
3,376
edits
TestEngineering/Performance/Talos/Misc: Difference between revisions
TestEngineering/Performance/Talos/Misc (view source)
Revision as of 15:24, 1 March 2018
, 1 March 2018→Steps to add a test to production: - first pass
(→History of tp Tests: - update) |
m (→Steps to add a test to production: - first pass) |
||
| Line 58: | Line 58: | ||
* [[https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos File a bug]] to add tests to [[https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/test.py talos]] [[https://bugzilla.mozilla.org/show_bug.cgi?id=893071 example]]. | * [[https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos File a bug]] to add tests to [[https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/test.py talos]] [[https://bugzilla.mozilla.org/show_bug.cgi?id=893071 example]]. | ||
* for aurora/central on desktop only - just land your new test to your in-tree commit (on inbound/autoland) and ensure that you adjust talos.json to run the test. | |||
** NOTE: one exception is adding an entirely new suite- this requires a [[http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla-tests/config.py#l176 buildbot]] patch to add the new scheduled job. Example: [[https://bugzilla.mozilla.org/show_bug.cgi?id=886288 Bug 886288 - deploy new tsvgx and tscrollx talos tests to m-c only]] | ** NOTE: one exception is adding an entirely new suite- this requires a [[http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla-tests/config.py#l176 buildbot]] patch to add the new scheduled job. Example: [[https://bugzilla.mozilla.org/show_bug.cgi?id=886288 Bug 886288 - deploy new tsvgx and tscrollx talos tests to m-c only]] | ||
** if you add a new suite, edit [https://searchfox.org/mozilla-central/source/taskcluster/ci/test/talos.yml talos.yml] to add the testname to a new suite, then add it to [https://searchfox.org/mozilla-central/source/taskcluster/ci/test/test-sets.yml test-sets.yml] for all the different talos test-sets. | |||
* Update talos | * Update talos | ||
** just land code in-tree (inbound/ | ** just land code in-tree (inbound/autoland) | ||
* Ensure the test follows the branch through the [[http://mozilla.github.io/process-releases/draft/development_overview/ release stages]] | * Ensure the test follows the branch through the [[http://mozilla.github.io/process-releases/draft/development_overview/ release stages]] | ||
** if we are just updating talos.json, this will be automatic | ** if we are just updating talos.json, this will be automatic | ||
* if this is an update to an existing test that could change the numbers, this needs to be treated as a new test and run side by side for a week to get a new baseline for the numbers. | * if this is an update to an existing test that could change the numbers, this needs to be treated as a new test and run side by side for a week to get a new baseline for the numbers. | ||
* [https:// | * document the test on [[https://wiki.mozilla.org/Buildbot/Talos/Tests]] | ||
** NOTE: this should be updated every time the branch moves closer to release. Once on release we don't need to update | ** NOTE: this should be updated every time the branch moves closer to release. Once on release we don't need to update | ||